From: "Darrick J. Wong" <djwong@kernel.org>
To: Zhang Yi <yi.zhang@huaweicloud.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-ext4@vger.kernel.org, brauner@kernel.org,
hch@infradead.org, joannelkoong@gmail.com, yi.zhang@huawei.com,
yizhang089@gmail.com, yangerkun@huawei.com, yukuai@fnnas.com
Subject: Re: [PATCH v2 1/5] iomap: correct the range of a partial dirty clear
Date: Wed, 8 Jul 2026 14:40:19 -0700 [thread overview]
Message-ID: <20260708214019.GE9368@frogsfrogsfrogs> (raw)
In-Reply-To: <20260520030357.679687-2-yi.zhang@huaweicloud.com>
On Wed, May 20, 2026 at 11:03:53AM +0800, Zhang Yi wrote:
> From: Zhang Yi <yi.zhang@huawei.com>
>
> The block range calculation in ifs_clear_range_dirty() is incorrect when
> partially clearing a range in a folio. We cannot clear the dirty bit of
> the first block or the last block if the start or end offset is not
> blocksize-aligned. This has not yet caused any issues since we always
> clear a whole folio in iomap_writeback_folio().
>
> Fix this by rounding up the first block to blocksize alignment, and
> calculate the last block by rounding down (using truncation). Correct
> the nr_blks calculation accordingly.
>
> Fixes: 4ce02c679722 ("iomap: Add per-block dirty state tracking to improve performance")
> Cc: <stable@vger.kernel.org> # v6.6
> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
My apologies for the unnecessary delay, I was on vacation when this came
through and I never saw it. :/
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/iomap/buffered-io.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index d7b648421a70..64351a448a8b 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -176,13 +176,17 @@ static void ifs_clear_range_dirty(struct folio *folio,
> {
> struct inode *inode = folio->mapping->host;
> unsigned int blks_per_folio = i_blocks_per_folio(inode, folio);
> - unsigned int first_blk = (off >> inode->i_blkbits);
> - unsigned int last_blk = (off + len - 1) >> inode->i_blkbits;
> - unsigned int nr_blks = last_blk - first_blk + 1;
> + unsigned int first_blk = round_up(off, i_blocksize(inode)) >>
> + inode->i_blkbits;
> + unsigned int last_blk = (off + len) >> inode->i_blkbits;
> unsigned long flags;
>
> + if (first_blk >= last_blk)
> + return;
> +
> spin_lock_irqsave(&ifs->state_lock, flags);
> - bitmap_clear(ifs->state, first_blk + blks_per_folio, nr_blks);
> + bitmap_clear(ifs->state, first_blk + blks_per_folio,
> + last_blk - first_blk);
> spin_unlock_irqrestore(&ifs->state_lock, flags);
> }
>
> --
> 2.52.0
>
>
next prev parent reply other threads:[~2026-07-08 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 3:03 [PATCH v2 0/5] iomap: trivial fixes for ext4 conversion Zhang Yi
2026-05-20 3:03 ` [PATCH v2 1/5] iomap: correct the range of a partial dirty clear Zhang Yi
2026-07-08 20:57 ` Joanne Koong
2026-07-09 2:36 ` Zhang Yi
2026-07-08 21:40 ` Darrick J. Wong [this message]
2026-07-09 2:47 ` Zhang Yi
2026-05-20 3:03 ` [PATCH v2 2/5] iomap: support invalidating partial folios Zhang Yi
2026-07-08 21:30 ` Joanne Koong
2026-05-20 3:03 ` [PATCH v2 3/5] iomap: fix incorrect did_zero setting in iomap_zero_iter() Zhang Yi
2026-05-20 3:03 ` [PATCH v2 4/5] iomap: fix out-of-bounds bitmap_set() with zero-length range Zhang Yi
2026-07-08 20:40 ` Joanne Koong
2026-07-08 23:26 ` Darrick J. Wong
2026-05-20 3:03 ` [PATCH v2 5/5] iomap: add comments for ifs_clear/set_range_dirty() Zhang Yi
2026-07-08 20:49 ` Joanne Koong
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=20260708214019.GE9368@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@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@fnnas.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