Re: fixes for iomap_bio_read_folio_range_sync

On Tue, 04 Aug 2026 05:43:56 -0700, Christoph Hellwig wrote:
> fixes for iomap_bio_read_folio_range_sync
> 
> Hi all,
> 
> two fixes for iomap_bio_read_folio_range_sync, a potential kernel
> crash when tweaking the device integrity behvavior using sysfs,
> and a missing bio_uninit that the Sashiko review of the first fix
> found.
> 
> [...]

Since the merge window is imminent I'm routing this through the iomap
branch and it's not really a fix for something in this merge window.

---

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

[1/2] iomap: don't free integrity payload that doesn't exist
      https://git.kernel.org/vfs/vfs/c/8a8685b32c07
[2/2] iomap: iomap_bio_read_folio_range_sync is missing a call to bio_uninit
      https://git.kernel.org/vfs/vfs/c/accb6624e383