On 10:10 26/02, Darrick J. Wong wrote: > On Wed, Feb 26, 2025 at 11:51:19AM -0500, Goldwyn Rodrigues wrote: > > If the current ioend is built for iomap with flags set to > > IOMAP_F_BOUNDARY and the next iomap does not have IOMAP_F_BOUNDARY set, > > IOMAP_F_BOUNDARY will not be respected because the iomap structure has > > been overwritten during the map_blocks call for the next iomap. Fix this > > by checking both iomap.flags and ioend->io_flags for IOMAP_F_BOUNDARY. > > Why is it necessary to avoid merging with an IOMAP_F_BOUNDARY ioend if > this new mapping isn't IOMAP_F_BOUNDARY? If the filesystem needs that, > it can set BOUNDARY on both mappings, right? Yes, you are right. Just that when filesystem wants to merge it would have to keep a track. But that's fine. I have figured out to solve my problem another way. -- Goldwyn
