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

2020-03-22 Thread Chao Yu
On 2020/3/22 22:56, Joe Perches wrote: > On Sun, 2020-03-22 at 21:56 +0800, Chao Yu wrote: >> From: 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 memor

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

2020-03-22 Thread Joe Perches
On Sun, 2020-03-22 at 21:56 +0800, Chao Yu wrote: > From: 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, corrupt

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

2020-03-22 Thread Chao Yu
From: 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