From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH 1/6] zloop: fix write pointer calculation in zloop_forget_cache
Date: Tue, 14 Apr 2026 11:26:06 +0200 [thread overview]
Message-ID: <5f49393f-a61b-41c4-94bb-aa05390f0307@kernel.org> (raw)
In-Reply-To: <20260414081811.549755-2-hch@lst.de>
On 4/14/26 10:17, Christoph Hellwig wrote:
> The write pointer is absolute and in sector units, so we need to
> convert it to a relative byte address first.
>
> Fixes: c505448748f7 ("zloop: forget write cache on force removal")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-04-14 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 8:17 zloop fixes Christoph Hellwig
2026-04-14 8:17 ` [PATCH 1/6] zloop: fix write pointer calculation in zloop_forget_cache Christoph Hellwig
2026-04-14 9:26 ` Damien Le Moal [this message]
2026-04-14 8:17 ` [PATCH 2/6] zloop: use vfs_truncate Christoph Hellwig
2026-04-14 9:26 ` Damien Le Moal
2026-04-14 8:17 ` [PATCH 3/6] zloop: improve the unaligned write pointer warning Christoph Hellwig
2026-04-14 9:27 ` Damien Le Moal
2026-04-14 8:17 ` [PATCH 4/6] zloop: set RQF_QUIET when completing requests on deleted devices Christoph Hellwig
2026-04-14 9:28 ` Damien Le Moal
2026-04-14 8:17 ` [PATCH 5/6] zloop: factor out zloop_mark_{full,empty} helpers Christoph Hellwig
2026-04-14 9:29 ` Damien Le Moal
2026-04-14 8:17 ` [PATCH 6/6] zloop: remove irq-safe locking Christoph Hellwig
2026-04-14 9:30 ` Damien Le Moal
2026-04-14 16:20 ` zloop fixes Johannes Thumshirn
2026-04-15 20:03 ` Jens Axboe
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=5f49393f-a61b-41c4-94bb-aa05390f0307@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/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