• E
    ext3: ext3_mark_recovery_complete() doesn't need to use lock_super · 4854a5f0
    Eric Sandeen 提交于
    The function ext3_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
    ext3_remount().
    
    Port of ext4 commit a63c9eb2 by
    Theodore Ts'o <tytso@mit.edu>.
    
    CC: Theodore Ts'o <tytso@mit.edu>
    Signed-off-by: NEric Sandeen <sandeen@redhat.com>
    Signed-off-by: NJan Kara <jack@suse.cz>
    4854a5f0
super.c 82.8 KB