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

On 11/23, Sheng Yong wrote: > 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

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

Hi Sheng, On 2018/11/23 20:11, Sheng Yong wrote: > 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 I

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:

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

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. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks, ___ Linux-f2fs-devel mailing list