aboutsummaryrefslogtreecommitdiffstats
path: root/mm/msync.c
diff options
context:
space:
mode:
authorJan Blunck <jblunck@suse.de>2010-04-14 14:38:39 +0200
committerJan Kara <jack@suse.cz>2010-05-21 19:30:40 +0200
commite0a5cbac029db69032758000c67465c2ed7a5736 (patch)
tree14d81b8fee8d43674acd4c63a2e994bdc3da774c /mm/msync.c
parentc15271f4e74cd6dbdf461335d6d1450949c4b956 (diff)
downloadkernel_samsung_tuna-e0a5cbac029db69032758000c67465c2ed7a5736.zip
kernel_samsung_tuna-e0a5cbac029db69032758000c67465c2ed7a5736.tar.gz
kernel_samsung_tuna-e0a5cbac029db69032758000c67465c2ed7a5736.tar.bz2
BKL: Remove BKL from ext2 filesystem
The BKL is still used in ext2_put_super(), ext2_fill_super(), ext2_sync_fs() ext2_remount() and ext2_write_inode(). From these calls ext2_put_super(), ext2_fill_super() and ext2_remount() are protected against each other by the struct super_block s_umount rw semaphore. The call in ext2_write_inode() could only protect the modification of the ext2_sb_info through ext2_update_dynamic_rev() against concurrent ext2_sync_fs() or ext2_remount(). ext2_fill_super() and ext2_put_super() can be left out because you need a valid filesystem reference in all three cases, which you do not have when you are one of these functions. If the BKL is only protecting the modification of the ext2_sb_info it can safely be removed since this is protected by the struct ext2_sb_info s_lock. Signed-off-by: Jan Blunck <jblunck@suse.de> Cc: Jan Kara <jack@suse.cz> Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'mm/msync.c')
0 files changed, 0 insertions, 0 deletions