diff options
author | Theodore Ts'o <tytso@mit.edu> | 2009-04-25 15:48:07 -0400 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2009-04-25 15:48:07 -0400 |
commit | 114e9fc90703bd6aac0229fb559e97caa6c49770 (patch) | |
tree | 722343de92b421c252a9e33b0e5e44955115080a /fs/ext4/super.c | |
parent | 8df9675f8b498d0bfa1f0b5b06f56bf1ff366dd5 (diff) | |
download | linux-next-114e9fc90703bd6aac0229fb559e97caa6c49770.tar.gz |
ext4: Remove outdated comment about lock_super()
ext4_fill_super() is no longer called by read_super(), and it is no
longer called with the superblock locked. The
unlock_super()/lock_super() is no longer present, so this comment is
entirely superfluous.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/super.c')
-rw-r--r-- | fs/ext4/super.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/fs/ext4/super.c b/fs/ext4/super.c index fcd7b24c6df3..e3b35f26d5fe 100644 --- a/fs/ext4/super.c +++ b/fs/ext4/super.c @@ -2828,14 +2828,6 @@ no_journal: goto failed_mount4; }; - /* - * akpm: core read_super() calls in here with the superblock locked. - * That deadlocks, because orphan cleanup needs to lock the superblock - * in numerous places. Here we just pop the lock - it's relatively - * harmless, because we are now ready to accept write_super() requests, - * and aviro says that's the only reason for hanging onto the - * superblock lock. - */ EXT4_SB(sb)->s_mount_state |= EXT4_ORPHAN_FS; ext4_orphan_cleanup(sb, es); EXT4_SB(sb)->s_mount_state &= ~EXT4_ORPHAN_FS; |