From: "Theodore Tso" <tytso@mit.edu>
To: brauner@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-ext4@vger.kernel.org, djwong@kernel.org, hch@infradead.org,
joannelkoong@gmail.com, yi.zhang@huawei.com,
yizhang089@gmail.com, chengzhihao1@huawei.com,
yangerkun@huawei.com,
yukuai@alb-78bjiv52429oh8qptp.cn-shenzhen.alb.aliyuncs.com,
Zhang Yi <yi.zhang@huaweicloud.com>
Subject: Re: [PATCH v4 0/5] iomap: trivial fixes for ext4 conversion
Date: Wed, 22 Jul 2026 11:34:17 -0400 [thread overview]
Message-ID: <amDiuuX56ChS6LO0@mit.edu> (raw)
In-Reply-To: <20260714082325.325163-1-yi.zhang@huaweicloud.com>
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
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/20260713072906.1726059-1-yi.zhang@huaweicloud.com/
> v2: https://lore.kernel.org/linux-fsdevel/20260520030357.679687-1-yi.zhang@huaweicloud.com/
> v1: https://lore.kernel.org/linux-fsdevel/20260514062955.1183976-1-yi.zhang@huaweicloud.com/
>
>
> 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/20260511072344.191271-1-yi.zhang@huaweicloud.com/
>
> 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
>
>
next prev parent reply other threads:[~2026-07-22 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 8:23 [PATCH v4 0/5] iomap: trivial fixes for ext4 conversion Zhang Yi
2026-07-14 8:23 ` [PATCH v4 1/5] iomap: correct the range of a partial dirty clear Zhang Yi
2026-07-14 8:23 ` [PATCH v4 2/5] iomap: support invalidating partial folios Zhang Yi
2026-08-03 7:13 ` Zhang Yi
2026-08-04 14:59 ` Brian Foster
2026-08-04 18:41 ` Darrick J. Wong
2026-08-05 2:42 ` Zhang Yi
2026-07-14 8:23 ` [PATCH v4 3/5] iomap: fix incorrect did_zero setting in iomap_zero_iter() Zhang Yi
2026-07-14 8:23 ` [PATCH v4 4/5] iomap: fix out-of-bounds bitmap_set() with zero-length range Zhang Yi
2026-07-14 8:23 ` [PATCH v4 5/5] iomap: add comments for ifs_clear/set_range_dirty() Zhang Yi
2026-07-22 15:34 ` Theodore Tso [this message]
2026-07-23 1:25 ` [PATCH v4 0/5] iomap: trivial fixes for ext4 conversion Zhang Yi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=amDiuuX56ChS6LO0@mit.edu \
--to=tytso@mit.edu \
--cc=brauner@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=joannelkoong@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@huaweicloud.com \
--cc=yizhang089@gmail.com \
--cc=yukuai@alb-78bjiv52429oh8qptp.cn-shenzhen.alb.aliyuncs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox