aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2009-04-25 15:48:07 -0400
committerTheodore Ts'o <tytso@mit.edu>2009-04-25 15:48:07 -0400
commit114e9fc90703bd6aac0229fb559e97caa6c49770 (patch)
tree722343de92b421c252a9e33b0e5e44955115080a
parent8df9675f8b498d0bfa1f0b5b06f56bf1ff366dd5 (diff)
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>
-rw-r--r--fs/ext4/super.c8
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:
2828 goto failed_mount4; 2828 goto failed_mount4;
2829 }; 2829 };
2830 2830
2831 /*
2832 * akpm: core read_super() calls in here with the superblock locked.
2833 * That deadlocks, because orphan cleanup needs to lock the superblock
2834 * in numerous places. Here we just pop the lock - it's relatively
2835 * harmless, because we are now ready to accept write_super() requests,
2836 * and aviro says that's the only reason for hanging onto the
2837 * superblock lock.
2838 */
2839 EXT4_SB(sb)->s_mount_state |= EXT4_ORPHAN_FS; 2831 EXT4_SB(sb)->s_mount_state |= EXT4_ORPHAN_FS;
2840 ext4_orphan_cleanup(sb, es); 2832 ext4_orphan_cleanup(sb, es);
2841 EXT4_SB(sb)->s_mount_state &= ~EXT4_ORPHAN_FS; 2833 EXT4_SB(sb)->s_mount_state &= ~EXT4_ORPHAN_FS;