diff options
| author | Jaegeuk Kim <jaegeuk@kernel.org> | 2016-05-04 19:48:53 -0700 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2016-05-07 10:32:30 -0700 |
| commit | 29234b1d6d2d4ecbd8f85831285c20329617859f (patch) | |
| tree | 59ca1e2fdc859feda1f25b4f43aa860661cc9db4 /fs/f2fs | |
| parent | f51b4ce6c1759a64d68d314545854dc226ab69a0 (diff) | |
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>
Diffstat (limited to 'fs/f2fs')
| -rw-r--r-- | fs/f2fs/inode.c | 16 |
1 files changed, 2 insertions, 14 deletions
diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c index baf3a2a1f249..689d6914e2e4 100644 --- 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); |