Re: [PATCH v4 0/5] iomap: trivial fixes for ext4 conversion
Zhang Yi <[email protected]>
| Newsgroups | org.kernel.vger.linux-ext4,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-xfs |
|---|---|
| Message-ID | <[email protected]> |
On 7/22/2026 11:34 PM, Theodore Tso wrote: > Hi Christian, > > These fixes are needed for landing support for buffered writes using > iomap in ext4. That won't be ready to land this development cycle, > but could we land these fixes now? > > Thanks, > > - Ted Here's another one. Could you please take this one along too? Thank you. https://lore.kernel.org/linux-fsdevel/[email protected]/ Best Regards Yi. > > On Tue, Jul 14, 2026 at 04:23:20PM -0500, Zhang Yi wrote: >> Hi, >> >> This is v4 of the trivial iomap fixes for the ext4 conversion. There are >> no code changes relative to v3, the only update is the addition of a >> Fixes tag in patch 03. >> >> Changes since v3: >> - Collect RVB tags from Christoph. >> - Add fix tag in patch patch 03 ("iomap: fix incorrect did_zero setting >> in iomap_zero_iter()"). >> Changes since v2: >> - Collect RVB tags from Darrick and Joanne. >> - Remove CC stable tag in patch 01 as Joanne suggested. >> Changes since v1: >> - Add fix tags to patch 01 and 04. >> - In patch 04, change ifs_set_range_uptodate() to always fall through >> to ifs_is_fully_uptodate(), preventing a false-positive uptodate >> mask. >> - Add patch 05, add comments for ifs_clear/set_range_dirty(). >> >> v3: https://lore.kernel.org/linux-fsdevel/[email protected]/ >> v2: https://lore.kernel.org/linux-fsdevel/[email protected]/ >> v1: https://lore.kernel.org/linux-fsdevel/[email protected]/ >> >> >> Original Cover-letter: >> >> This patch series contains a few trivial iomap-related fixes in >> preparation for converting ext4 buffered I/O to use iomap. >> >> The first three patches are taken from my ext4 conversion series [1], as >> suggested by Christoph. The fourth patch fixes a bug originally reported >> by Sashiko during review of my series; although unrelated to the ext4 >> conversion, it is worth fixing on its own. Please see the following >> patches for detail. The fifth patch add comments for >> ifs_clear/set_range_dirty(), and the last patch avoids merging ioends >> that have different private data. >> >> Thanks, >> Yi. >> >> [1] https://lore.kernel.org/linux-ext4/[email protected]/ >> >> Zhang Yi (5): >> iomap: correct the range of a partial dirty clear >> iomap: support invalidating partial folios >> iomap: fix incorrect did_zero setting in iomap_zero_iter() >> iomap: fix out-of-bounds bitmap_set() with zero-length range >> iomap: add comments for ifs_clear/set_range_dirty() >> >> fs/iomap/buffered-io.c | 58 ++++++++++++++++++++++++++++++++---------- >> 1 file changed, 44 insertions(+), 14 deletions(-) >> >> -- >> 2.52.0 >> >>