Re: (subset) [PATCH v5 00/22] iomap: convert to in-iter iomap_next() model

On Wed, 29 Jul 2026 12:27:15 -0700, Joanne Koong wrote:

This series implements a suggestion by Christoph for finishing the conversion
of iomap to an iterator model. This revives Matthew's previous RFC [1], which
had the same intention.

Every iomap operation currently drives its iteration through a struct
iomap_ops, which contains two callbacks, ->iomap_begin() and ->iomap_end().
iomap_iter() only ever sees these as pointers, so every step of every
iteration is an indirect call, including on the hottest paths.

[...]

Applied to the vfs-7.3.iomap.final branch of the vfs/vfs.git tree.
Patches in the vfs-7.3.iomap.final 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-7.3.iomap.final

[20/22] iomap: remove ->iomap_begin()/->iomap_end() legacy path
        https://git.kernel.org/vfs/vfs/c/71864822ce32
[21/22] iomap: pass iomap_iter_next_fn directly instead of struct iomap_ops
        https://git.kernel.org/vfs/vfs/c/2a3b6fe7a17f
[22/22] Documentation: iomap: update docs to reflect iomap_iter_next model
        https://git.kernel.org/vfs/vfs/c/e16ceb1b6c03