f2fs: don't worry about inode leak in evict_inode

Even if an inode failed to release its blocks, it should be kept in an orphan
inode list, so it will be released later.

Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index baf3a2a1f2490a4656590998ea3c9004e42171c6..689d6914e2e405cd2788ccafb3e6bea5b1fd2dd0 100644 (file)
--- a/fs/f2fs/inode.c
+++ b/fs/f2fs/inode.c
@@ -377,20 +377,8 @@ no_delete:
                alloc_nid_failed(sbi, inode->i_ino);
                clear_inode_flag(fi, FI_FREE_NID);
        }
-
-       if (err && err != -ENOENT) {
-               if (!exist_written_data(sbi, inode->i_ino, ORPHAN_INO)) {
-                       /*
-                        * get here because we failed to release resource
-                        * of inode previously, reminder our user to run fsck
-                        * for fixing.
-                        */
-                       set_sbi_flag(sbi, SBI_NEED_FSCK);
-                       f2fs_msg(sbi->sb, KERN_WARNING,
-                               "inode (ino:%lu) resource leak, run fsck "
-                               "to fix this issue!", inode->i_ino);
-               }
-       }
+       f2fs_bug_on(sbi, err &&
+               !exist_written_data(sbi, inode->i_ino, ORPHAN_INO));
 out_clear:
        fscrypt_put_encryption_info(inode, NULL);
        clear_inode(inode);