Hi Christian,
On 2026/6/19 18:15, Christian Brauner wrote:
On Fri, 19 Jun 2026 07:00:53 +0200, Christoph Hellwig wrote:
Currently the iomap buffered read path tries to build up read context
(i.e. bios for the typical block based case) over multiple iomaps as
long as the sector matches. This does not take into account files
that can map to multiple different devices. While this could be fixed
by a bdev check in iomap_bio_read_folio_range, the building up of I/O
over iomaps actually was a problem for the not yet merged ext2 iomap
port, as that does want to send out I/O at the end of an indirect
block mapped range.
[...]
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.
btw, could we address this issue in the 7.2 cycle?
Not because that is a quite common case and needs a rush fix,
but Just because that can be reproducible under given
circumstances and users can get corrupted data.
Or if we need to hear thoughts from others, I think we could
delay one or two weeks though.
Thanks,
Gao Xiang
