From: John Garry <john.garry@linux.dev>
To: Niklas Cassel <cassel@kernel.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <mkp@kernel.org>
Cc: linux-scsi@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v4 02/10] scsi: scsi_debug: Make atomic writes and ZBC emulation mutually exclusive
Date: Fri, 18 Sep 2026 08:21:00 +0100 [thread overview]
Message-ID: <f2f03175-63a2-4077-8c11-970dad2896de@linux.dev> (raw)
In-Reply-To: <20260918062910.1709791-14-cassel@kernel.org>
On 9/18/26 07:29, Niklas Cassel wrote:
> There are no SMR drives that support atomic writes. Emulating a device
> that supports both is emulating something that a user cannot encounter,
> rather than the drives that exist, and it means maintaining the zone
> handling of a command that no zoned device implements.
>
> Nothing in the standards forbids the combination. For what would be by
> far the most common case, a host managed SMR drive whose logical block
> size equals its physical block size, there is no problem in the two
> features being combined: the drive vendor only has to give atomic
> writes an alignment that makes sense with regards to ZBC, for instance
> equal to the physical block size. This is therefore a choice not to
> complicate scsi_debug, rather than a restriction that the standards
> impose.
>
> Refuse the combination at initialisation. If SMR drives that support
> atomic writes ever become a thing, this can be changed back.
>
> Suggested-by: Damien Le Moal <dlemoal@kernel.org>
> Assisted-by: LLM
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
Reviewed-by: John Garry <john.garry@linux.dev>
> ---
> Tested by loading the module with each combination:
>
> zbc=managed atomic_wr=1 refused, -EINVAL
> zbc=aware atomic_wr=1 refused, -EINVAL
> zbc=managed loads
> atomic_wr=1 loads
> ---
> drivers/scsi/scsi_debug.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
> index c664966e95cb..8e45a57ae406 100644
> --- a/drivers/scsi/scsi_debug.c
> +++ b/drivers/scsi/scsi_debug.c
> @@ -8739,6 +8739,11 @@ static int __init scsi_debug_init(void)
> return -EINVAL;
> }
>
> + if (sdeb_zbc_in_use && sdebug_atomic_wr) {
> + pr_err("atomic_wr is not supported by a zoned device\n");
> + return -EINVAL;
> + }
> +
> if (sdebug_dev_size_mb == DEF_DEV_SIZE_PRE_INIT)
> sdebug_dev_size_mb = DEF_DEV_SIZE_MB;
> if (sdebug_dev_size_mb < 1)
next prev parent reply other threads:[~2026-09-18 7:21 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 [this message]
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
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=f2f03175-63a2-4077-8c11-970dad2896de@linux.dev \
--to=john.garry@linux.dev \
--cc=James.Bottomley@HansenPartnership.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox