Re: [f2fs-dev] [RFC PATCH] f2fs: fix compress file start atomic write may cause data corruption

2022-03-06 Thread 常凤楠 via Linux-f2fs-devel
> -Original Message- > From: Chao Yu > Sent: Monday, March 7, 2022 9:43 AM > To: Fengnan Chang ; [email protected] > Cc: [email protected]; 常凤楠 > > Subject: Re: [RFC PATCH] f2fs: fix compress file start atomic write may cause > data corruption > > On 2022/3/5 12:00

[f2fs-dev] [PATCH -next] f2fs: remove unnecessary read for F2FS_FITS_IN_INODE

2022-03-06 Thread Jia Yang via Linux-f2fs-devel
F2FS_FITS_IN_INODE only cares the type of f2fs inode, so there is no need to read node page of f2fs inode. Signed-off-by: Jia Yang --- fs/f2fs/file.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index cfdc41f87f5d..4b93fbec2ec0 10

Re: [f2fs-dev] [RFC PATCH] f2fs: fix compress file start atomic write may cause data corruption

2022-03-06 Thread Chao Yu
On 2022/3/5 12:00, Fengnan Chang wrote: When compressed file has blocks, start atomic write will be failed, but You mean f2fs_ioc_start_atomic_write will succeed, but compressed flag will be remained in inode? still set FI_ATOMIC_FILE flag, if write partial cluster and commit atomic write wil