On Fri, 15 Nov 2024 09:59:31 -0500, Brian Foster wrote: > iomap_zero_range() uses buffered writes for manual zeroing, no > longer updates i_size for such writes, but is still explicitly > called for post-eof ranges. The historical use case for this is > zeroing post-eof speculative preallocation on extending writes from > XFS. However, XFS also recently changed to convert all post-eof > delalloc mappings to unwritten in the iomap_begin() handler, which > means it now never expects manual zeroing of post-eof mappings. In > other words, all post-eof mappings should be reported as holes or > unwritten. > > [...] Applied to the vfs.fixes branch of the vfs/vfs.git tree. Patches in the vfs.fixes branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs.fixes [1/1] iomap: warn on zero range of a post-eof folio https://git.kernel.org/vfs/vfs/c/2eba5b6013a5
