Re: [f2fs-dev] [PATCH 1/4] f2fs: propagate error given by f2fs_find_entry

2016-05-29 Thread Jaegeuk Kim
On Fri, May 27, 2016 at 12:48:48PM +0800, He YunLei wrote: > On 2016/5/27 8:25, Jaegeuk Kim wrote: > >If we get ENOMEM or EIO in f2fs_find_entry, we should stop right away. > >Otherwise, for example, we can get duplicate directory entry by ->chash and > >->clevel. > > > >Signed-off-by: Jaegeuk Kim

Re: [f2fs-dev] [PATCH 1/4] f2fs: propagate error given by f2fs_find_entry

2016-05-26 Thread He YunLei
On 2016/5/27 8:25, Jaegeuk Kim wrote: > If we get ENOMEM or EIO in f2fs_find_entry, we should stop right away. > Otherwise, for example, we can get duplicate directory entry by ->chash and > ->clevel. > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/dir.c| 23

[f2fs-dev] [PATCH 1/4] f2fs: propagate error given by f2fs_find_entry

2016-05-26 Thread Jaegeuk Kim
If we get ENOMEM or EIO in f2fs_find_entry, we should stop right away. Otherwise, for example, we can get duplicate directory entry by ->chash and ->clevel. Signed-off-by: Jaegeuk Kim --- fs/f2fs/dir.c| 23 --- fs/f2fs/inline.c | 4 +++-