If we got failure from both of create and evict_inode, we can hit this wrong
bug_on.

Signed-off-by: Jaegeuk Kim <jaeg...@kernel.org>
---
 fs/f2fs/inode.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index e53c784ab11e..5673b0bd83b5 100644
--- a/fs/f2fs/inode.c
+++ b/fs/f2fs/inode.c
@@ -426,8 +426,6 @@ void f2fs_evict_inode(struct inode *inode)
                alloc_nid_failed(sbi, inode->i_ino);
                clear_inode_flag(inode, FI_FREE_NID);
        }
-       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);
-- 
2.13.0.rc1.294.g07d810a77f-goog

Reply via email to