The patch titled Subject: fs/ufs: remove extra superblock write on unmount has been removed from the -mm tree. Its filename was fs-ufs-remove-extra-superblock-write-on-unmount.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Artem Bityutskiy <artem.bityutskiy@xxxxxxxxxxxxxxx> Subject: fs/ufs: remove extra superblock write on unmount This patchset makes UFS file-system stop using the VFS '->write_supers()' call-back and the '->s_dirt' superblock field because I plan to remove them once all users are gone. Like some other similar patch-sets (affs, hfs, hfsplus, reiserfs), we switch to a delayed job for writing out the superblock instead of using the 's_dirt' flag. Additionally, this patch-set includes several clean-ups. Tested using the fsstress test from the LTP project. This patch: remove extra superblock write on unmount UFS calls 'ufs_write_super()' from 'ufs_put_super()' in order to write the superblocks to the media. However, it is not needed because VFS calls '->sync_fs()' before calling '->put_super()' - so by the time we are in 'ufs_write_super()', the superblocks are already synchronized. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@xxxxxxxxxxxxxxx> Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx> Cc: Evgeniy Dushistov <dushistov@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/ufs/super.c | 3 --- 1 file changed, 3 deletions(-) diff -puN fs/ufs/super.c~fs-ufs-remove-extra-superblock-write-on-unmount fs/ufs/super.c --- a/fs/ufs/super.c~fs-ufs-remove-extra-superblock-write-on-unmount +++ a/fs/ufs/super.c @@ -1238,9 +1238,6 @@ static void ufs_put_super(struct super_b UFSD("ENTER\n"); - if (sb->s_dirt) - ufs_write_super(sb); - if (!(sb->s_flags & MS_RDONLY)) ufs_put_super_internal(sb); _ Patches currently in -mm which might be from artem.bityutskiy@xxxxxxxxxxxxxxx are linux-next.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html