Re: [f2fs-dev] [PATCH] f2fs: check memory boundary by insane namelen

Hi, Jaegeuk and Chao, On 2018/11/15 15:50, Jaegeuk Kim wrote: If namelen is corrupted to have very long value, fill_dentries can copy wrong memory area. Is there any scenario that could hit this corruption? Or this is triggered by fuzzing injection? thanks, Sheng Yong Signed-off-by: Jaegeuk

Re: [f2fs-dev] [PATCH 1/2] f2fs: remove stale inode entry before eviction from gdirty_list

Hi Chao, On 11/21/2018 9:00 AM, Chao Yu wrote: Hi Ritesh, On 2018/11/20 18:33, Ritesh Harjani wrote: On 11/20/2018 2:33 AM, Jaegeuk Kim wrote: On 11/19, Ritesh Harjani wrote: Hi Chao, On 11/19/2018 12:09 PM, Chao Yu wrote: Hi Ritesh, On 2018/11/19 14:02, Ritesh Harjani wrote: This is see

Re: [f2fs-dev] [PATCH 1/2] f2fs: fix sbi->extent_list corruption issue

On Fri, Nov 23, 2018 at 05:52:16PM +0800, Chao Yu wrote: > On 2018/11/23 11:42, Sahitya Tummala wrote: > > On Thu, Nov 22, 2018 at 04:11:07AM -0800, Jaegeuk Kim wrote: > >> On 11/22, Chao Yu wrote: > >>> On 2018/11/22 18:59, Sahitya Tummala wrote: > When there is a failure in f2fs_fill_super()

Re: [f2fs-dev] [PATCH 1/2] f2fs: fix sbi->extent_list corruption issue

On 2018/11/23 11:42, Sahitya Tummala wrote: > On Thu, Nov 22, 2018 at 04:11:07AM -0800, Jaegeuk Kim wrote: >> On 11/22, Chao Yu wrote: >>> On 2018/11/22 18:59, Sahitya Tummala wrote: When there is a failure in f2fs_fill_super() after/during the recovery of fsync'd nodes, it frees the curr