aboutsummaryrefslogtreecommitdiff
path: root/fs/autofs4
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2009-05-01 01:59:42 -0400
committerTheodore Ts'o <tytso@mit.edu>2009-05-01 01:59:42 -0400
commita63c9eb2ce6f5028da90f282798232c4f398ceb8 (patch)
tree3b32193dfc80a3925f5ea5a6545765f5176a6f2d /fs/autofs4
parent114e9fc90703bd6aac0229fb559e97caa6c49770 (diff)
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>
Diffstat (limited to 'fs/autofs4')
0 files changed, 0 insertions, 0 deletions