Re: [f2fs-dev] [PATCH v5] f2fs: fix potential .flags overflow on 32bit architecture

2020-03-24 Thread Chao Yu
On 2020/3/23 23:10, Jaegeuk Kim wrote: > On 03/23, Joe Perches wrote: >> On Mon, 2020-03-23 at 11:18 +0800, Chao Yu wrote: >>> f2fs_inode_info.flags is unsigned long variable, it has 32 bits >>> in 32bit architecture, since we introduced FI_MMAP_FILE flag >>> when we support data compression, we

Re: [f2fs-dev] [PATCH v5] f2fs: fix potential .flags overflow on 32bit architecture

2020-03-23 Thread Jaegeuk Kim
On 03/23, Joe Perches wrote: > On Mon, 2020-03-23 at 11:18 +0800, Chao Yu wrote: > > f2fs_inode_info.flags is unsigned long variable, it has 32 bits > > in 32bit architecture, since we introduced FI_MMAP_FILE flag > > when we support data compression, we may access memory cross > > the border of

Re: [f2fs-dev] [PATCH v5] f2fs: fix potential .flags overflow on 32bit architecture

2020-03-23 Thread Joe Perches
On Mon, 2020-03-23 at 11:18 +0800, Chao Yu wrote: > f2fs_inode_info.flags is unsigned long variable, it has 32 bits > in 32bit architecture, since we introduced FI_MMAP_FILE flag > when we support data compression, we may access memory cross > the border of .flags field, corrupting .i_sem field,

[f2fs-dev] [PATCH v5] f2fs: fix potential .flags overflow on 32bit architecture

2020-03-22 Thread Chao Yu
f2fs_inode_info.flags is unsigned long variable, it has 32 bits in 32bit architecture, since we introduced FI_MMAP_FILE flag when we support data compression, we may access memory cross the border of .flags field, corrupting .i_sem field, result in below deadlock. To fix this issue, let's expand