Re: [f2fs-dev] [PATCH v4 2/2] f2fs: fix to zero post-EOF data when extending file size
Chao Yu via Linux-f2fs-devel <[email protected]> Tue, 11 Aug 2026 15:17:20 +0800
| Newsgroups | net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 8/10/26 16:52, Zhiguo Niu wrote: > Chao Yu via Linux-f2fs-devel <[email protected]> >> When extending file size (e.g. via truncate, fallocate, or write) across an >> unaligned EOF boundary, we need to ensure that post-EOF data in the partial >> page is zeroed out in pagecache and marked dirty, meanwhile, tagging the inode >> with FI_ZERO_POST_EOF, so that following checkpoint() and fsync() can persist > Hi Chao, > It looks like this version doesn't have this flag "FI_ZERO_POST_EOF"? Thanks for catching this, fixed in v5. Thanks, > thanks! _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel