Theodore Ts'o a63c9eb2ce ext4: ext4_mark_recovery_complete() doesn't need to use lock_super
The function ext4_mark_recovery_complete() is called from two call
paths: either (a) while mounting the filesystem, in which case there's
no danger of any other CPU calling write_super() until the mount is
completed, and (b) while remounting the filesystem read-write, in
which case the fs core has already locked the superblock.  This also
allows us to take out a very vile unlock_super()/lock_super() pair in
ext4_remount().

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2009-05-01 01:59:42 -04:00
..
2009-03-31 23:00:26 -04:00
2008-10-10 20:02:48 -04:00
2009-03-31 09:10:09 -04:00
2009-02-26 01:04:07 -05:00
2008-10-10 20:02:48 -04:00
2009-03-27 17:16:58 -04:00
2008-10-10 20:02:48 -04:00
2008-10-10 20:02:48 -04:00