From: Bart Van Assche <bvanassche@acm.org>
To: Keith Busch <kbusch@meta.com>,
axboe@kernel.dk, dlemoal@kernel.org, johannes.thumshirn@wdc.com,
linux-block@vger.kernel.org
Cc: Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] null_blk: fix zone read length beyond write pointer
Date: Wed, 12 Nov 2025 09:00:38 -0800 [thread overview]
Message-ID: <4e9652f1-b2c6-4672-a39f-cdaa5560041b@acm.org> (raw)
In-Reply-To: <20251112164218.816774-1-kbusch@meta.com>
On 11/12/25 8:42 AM, Keith Busch wrote:
> Fix up the divisor calculating the number of zone sectors being read and
> handle a read that straddles the zone write pointer. The length is
> rounded up a sector boundary, so be sure to truncate any excess bytes
> off to avoid copying past the data segment.
Tested-by: Bart van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2025-11-12 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 16:42 [PATCH] null_blk: fix zone read length beyond write pointer Keith Busch
2025-11-12 17:00 ` Bart Van Assche [this message]
2025-11-12 17:03 ` Jens Axboe
2025-11-12 17:38 ` Chaitanya Kulkarni
2025-11-13 2:44 ` Damien Le Moal
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=4e9652f1-b2c6-4672-a39f-cdaa5560041b@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--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