On Tue, 06 May 2025 09:41:12 -0400, Brian Foster wrote: > Here's a bit more fallout and prep. work associated with the folio batch > prototype posted a while back [1]. Work on that is still pending so it > isn't included here, but based on the iter advance cleanups most of > these seemed worthwhile as standalone cleanups. Mainly this just cleans > up some of the helpers and pushes some pos/len trimming further down in > the write begin path. > > [...] Applied to the vfs-6.16.iomap branch of the vfs/vfs.git tree. Patches in the vfs-6.16.iomap 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-6.16.iomap [1/6] iomap: resample iter->pos after iomap_write_begin() calls https://git.kernel.org/vfs/vfs/c/e356c5d5b10e [2/6] iomap: drop unnecessary pos param from iomap_write_[begin|end] https://git.kernel.org/vfs/vfs/c/99fe6e61fd3c [3/6] iomap: drop pos param from __iomap_[get|put]_folio() https://git.kernel.org/vfs/vfs/c/3ceb65b17676 [4/6] iomap: helper to trim pos/bytes to within folio https://git.kernel.org/vfs/vfs/c/c4f9a1ba747d [5/6] iomap: push non-large folio check into get folio path https://git.kernel.org/vfs/vfs/c/c0f8658a9dbc [6/6] iomap: rework iomap_write_begin() to return folio offset and length https://git.kernel.org/vfs/vfs/c/66c0d8551428
