From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <mkp@kernel.org>,
linux-scsi@vger.kernel.org, John Garry <john.garry@linux.dev>
Subject: Re: [PATCH v4 07/10] scsi: scsi_debug: Do not write a partial physical block to a zoned device
Date: Fri, 18 Sep 2026 12:25:20 +0200 [thread overview]
Message-ID: <aq0RkLjApqzC96mP@ryzen> (raw)
In-Reply-To: <cbae6ecb-21da-4fac-8a44-ba9072009159@kernel.org>
On Fri, Sep 18, 2026 at 04:31:23PM +0700, Damien Le Moal wrote:
> On 2026/09/18 13:29, Niklas Cassel wrote:
> > do_device_access() copies one logical block at a time and stops at the
> > first short copy, so when the data-out buffer is smaller than the
> > transfer length of the command it can write part of a physical block.
> > An initiator can arrange that with SG_IO.
> >
> > A write that does not end on a physical block boundary is perfectly
> > acceptable to a device that is not zoned, and to a conventional zone,
> > where the device reads, modifies and writes the physical block that the
> > write falls in. ZBC-3 r06 (T10/BSR INCITS 579), 4.5.3.3.2, does require
> > a write to a sequential write required zone to end on a physical block
> > boundary, though, so a partly written physical block is not a state that
> > such a zone can be left in.
> >
> > Stop at the last whole physical block that the buffer holds, for a
> > sequential write required zone only. The bytes that are left over are
> > not written, and are reported to the initiator as part of the residual.
> >
> > With the default physblk_exp=0 the physical block size equals the
> > logical block size and this changes nothing. Nothing changes either when
> > the buffer holds all of the data that the command asks for, so a command
> > that transfers fewer logical blocks than a physical block is unaffected
> > wherever it is legal.
> >
> > Assisted-by: LLM
> > Signed-off-by: Niklas Cassel <cassel@kernel.org>
>
> A bit shift would be nicer than a division... But nevertheless, looks good.
>
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Sure, will apply the following change for this patch:
diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
index 5ae1241e4d8b..bbd675ca47f2 100644
--- a/drivers/scsi/scsi_debug.c
+++ b/drivers/scsi/scsi_debug.c
@@ -4313,7 +4313,8 @@ static int do_device_access(struct sdeb_store_info *sip, struct scsi_cmnd *scp,
struct sdeb_zone_state *zsp = zbc_zone(devip, lba);
if (zsp->z_type == ZBC_ZTYPE_SWR) {
- u32 avail = (sdb->length - sg_skip) / sdebug_sector_size;
+ u32 avail = (sdb->length - sg_skip)
+ >> ilog2(sdebug_sector_size);
if (avail < num)
num = round_down(avail, 1U << sdebug_physblk_exp);
And the following change for patch "scsi: scsi_debug: Advance the write
pointer over the data written":
@@ -5184,7 +5185,7 @@ static int resp_write_dt0(struct scsi_cmnd *scp, struct sdebug_dev_info *devip)
/* If ZBC zone then bump its write pointer over the data written */
if (sdebug_dev_is_zoned(devip) && ret > 0)
- zbc_inc_wp(devip, lba, ret / sdebug_sector_size);
+ zbc_inc_wp(devip, lba, ret >> ilog2(sdebug_sector_size));
if (meta_data_locked)
sdeb_meta_write_unlock(sip);
@@ -5350,7 +5351,8 @@ static int resp_write_scat(struct scsi_cmnd *scp,
ret = do_device_access(sip, scp, sg_off, lba, num, group, true, true);
/* If ZBC zone then bump its write pointer over the data written */
if (sdebug_dev_is_zoned(devip) && ret > 0)
- zbc_inc_wp(devip, lba, ret / sdebug_sector_size);
+ zbc_inc_wp(devip, lba,
+ ret >> ilog2(sdebug_sector_size));
if (unlikely(scsi_debug_lbp()))
map_region(sip, lba, num);
if (unlikely(-1 == ret)) {
when respinning.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-09-18 10:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 6:29 [PATCH v4 00/10] scsi: scsi_debug: fix zoned write validation Niklas Cassel
2026-09-18 6:29 ` [PATCH v4 01/10] scsi: scsi_debug: Refuse a zoned device with a non-zero lowest aligned LBA Niklas Cassel
2026-09-18 9:26 ` Damien Le Moal
2026-09-18 6:29 ` [PATCH v4 02/10] scsi: scsi_debug: Make atomic writes and ZBC emulation mutually exclusive Niklas Cassel
2026-09-18 7:21 ` John Garry
2026-09-18 9:26 ` Damien Le Moal
2026-09-18 6:29 ` [PATCH v4 03/10] scsi: scsi_debug: Take the zone metadata lock before the data lock Niklas Cassel
2026-09-18 9:28 ` Damien Le Moal
2026-09-18 6:29 ` [PATCH v4 04/10] scsi: scsi_debug: Evaluate scsi_debug_lbp() only once Niklas Cassel
2026-09-18 9:29 ` Damien Le Moal
2026-09-18 6:29 ` [PATCH v4 05/10] scsi: scsi_debug: Report the residual of a write Niklas Cassel
2026-09-18 6:29 ` [PATCH v4 06/10] scsi: scsi_debug: Enforce physical block alignment of zoned writes Niklas Cassel
2026-09-18 6:29 ` [PATCH v4 07/10] scsi: scsi_debug: Do not write a partial physical block to a zoned device Niklas Cassel
2026-09-18 9:31 ` Damien Le Moal
2026-09-18 10:25 ` Niklas Cassel [this message]
2026-09-18 6:29 ` [PATCH v4 08/10] scsi: scsi_debug: Advance the write pointer over the data written Niklas Cassel
2026-09-18 6:29 ` [PATCH v4 09/10] scsi: scsi_debug: Map the region written by WRITE ATOMIC (16) Niklas Cassel
2026-09-18 7:29 ` John Garry
2026-09-18 8:09 ` Niklas Cassel
2026-09-18 6:29 ` [PATCH v4 10/10] scsi: scsi_debug: Validate the access parameters of " Niklas Cassel
2026-09-18 7:33 ` John Garry
2026-09-18 7:53 ` Niklas Cassel
2026-09-18 8:19 ` John Garry
2026-09-18 8:55 ` Niklas Cassel
2026-09-18 9:32 ` 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=aq0RkLjApqzC96mP@ryzen \
--to=cassel@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dlemoal@kernel.org \
--cc=john.garry@linux.dev \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.