summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2010-10-24 09:50:11 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2010-10-25 21:23:01 -0400
commit70fd136ecc44ca8c364f4412f447de1d940c3639 (patch)
treebf4d4a83082816067093922363448821e1a393f2 /fs
parent9dcefee508d547eed88f3c578dc92819bdeaa952 (diff)
ntfs: don't call invalidate_inodes()
We are in fill_super(); again, no inodes with zero i_count could be around until we set MS_ACTIVE. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs')
-rw-r--r--fs/ntfs/super.c15
1 files changed, 0 insertions, 15 deletions
diff --git a/fs/ntfs/super.c b/fs/ntfs/super.c
index 19c5180f8a28..d4dec2d32117 100644
--- a/fs/ntfs/super.c
+++ b/fs/ntfs/super.c
@@ -3021,21 +3021,6 @@ iput_tmp_ino_err_out_now:
if (vol->mft_ino && vol->mft_ino != tmp_ino)
iput(vol->mft_ino);
vol->mft_ino = NULL;
- /*
- * This is needed to get ntfs_clear_extent_inode() called for each
- * inode we have ever called ntfs_iget()/iput() on, otherwise we A)
- * leak resources and B) a subsequent mount fails automatically due to
- * ntfs_iget() never calling down into our ntfs_read_locked_inode()
- * method again... FIXME: Do we need to do this twice now because of
- * attribute inodes? I think not, so leave as is for now... (AIA)
- */
- if (invalidate_inodes(sb)) {
- ntfs_error(sb, "Busy inodes left. This is most likely a NTFS "
- "driver bug.");
- /* Copied from fs/super.c. I just love this message. (-; */
- printk("NTFS: Busy inodes after umount. Self-destruct in 5 "
- "seconds. Have a nice day...\n");
- }
/* Errors at this stage are irrelevant. */
err_out_now:
sb->s_fs_info = NULL;