Re: [f2fs-dev] [PATCH 1/2] f2fs: don't need to invalidate wrong node page

On 2017/3/9 5:35, Jaegeuk Kim wrote: > On 03/08, Chao Yu wrote: >> On 2017/3/7 5:51, Jaegeuk Kim wrote: >>> If f2fs_new_inode() is failed, the bad inode will invalidate 0'th node page >>> during f2fs_evict_inode(), which doesn't need to do. >> >> Hmm...should not allow other using of inode->i_ino i

Re: [f2fs-dev] [PATCH 1/2] f2fs: don't need to invalidate wrong node page

On 03/08, Chao Yu wrote: > On 2017/3/7 5:51, Jaegeuk Kim wrote: > > If f2fs_new_inode() is failed, the bad inode will invalidate 0'th node page > > during f2fs_evict_inode(), which doesn't need to do. > > Hmm...should not allow other using of inode->i_ino in following codes of > f2fs_evict_inode,

Re: [f2fs-dev] [PATCH 1/2] f2fs: don't need to invalidate wrong node page

On 2017/3/7 5:51, Jaegeuk Kim wrote: > If f2fs_new_inode() is failed, the bad inode will invalidate 0'th node page > during f2fs_evict_inode(), which doesn't need to do. Hmm...should not allow other using of inode->i_ino in following codes of f2fs_evict_inode, right? Thanks, > > Signed-off-by:

[PATCH 1/2] f2fs: don't need to invalidate wrong node page

If f2fs_new_inode() is failed, the bad inode will invalidate 0'th node page during f2fs_evict_inode(), which doesn't need to do. Signed-off-by: Jaegeuk Kim --- fs/f2fs/inode.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c index 24bb8213