From: Niklas Cassel <cassel@kernel.org>
To: John Garry <john.garry@linux.dev>
Cc: "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <mkp@kernel.org>,
linux-scsi@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v4 09/10] scsi: scsi_debug: Map the region written by WRITE ATOMIC (16)
Date: Fri, 18 Sep 2026 10:09:56 +0200 [thread overview]
Message-ID: <aqzx1AUJExRHuz4S@ryzen> (raw)
In-Reply-To: <9838197a-4c2f-477c-b4bb-648f13922e19@linux.dev>
On Fri, Sep 18, 2026 at 08:29:15AM +0100, John Garry wrote:
> On 9/18/26 07:29, Niklas Cassel wrote:
> > When logical block provisioning is enabled, a command that writes user
> > data marks the region that it wrote in the provisioning map, so that
> > GET LBA STATUS reports the region as mapped. resp_write_dt0(),
> > resp_write_scat() and resp_write_same() all call map_region() for that.
> >
> > resp_atomic_write() does not, so a WRITE ATOMIC (16) leaves the
> > provisioning map untouched, and GET LBA STATUS keeps reporting the
> > region as deallocated after it has been written. map_state(), which
> > GET LBA STATUS uses, is the only reader of the map, so that is the whole
> > of the effect.
> >
> > Call map_region() the way resp_write_dt0() does, and take the zone
> > metadata write lock across the access as it does when logical block
> > provisioning is enabled. That lock is what serialises the provisioning
> > map against resp_unmap(), which holds it while unmap_region() clears map
> > bits and zeroes the data that they cover. resp_unmap() does nothing
> > unless logical block provisioning is enabled, so the lock is only needed
> > in that case.
> >
> > Assisted-by: LLM
> > Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> > Fixes: 84f3a3c01d70 ("scsi: scsi_debug: Atomic write support")
> > Signed-off-by: Niklas Cassel <cassel@kernel.org>
> > ---
> > Tested with:
> >
> > modprobe scsi_debug sector_size=512 physblk_exp=3 dev_size_mb=128 \
> > atomic_wr=1 lbpu=1
> >
> > GET LBA STATUS reports a region that has never been written as
> > deallocated, and reports it as mapped after a WRITE ATOMIC (16) of eight
> > blocks. Only an ordinary WRITE did so before this patch.
> > ---
> > drivers/scsi/scsi_debug.c | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
> > index cdea21b570c4..5243401701f9 100644
> > --- a/drivers/scsi/scsi_debug.c
> > +++ b/drivers/scsi/scsi_debug.c
> > @@ -6200,6 +6200,8 @@ static int resp_atomic_write(struct scsi_cmnd *scp,
> > u8 *cmd = scp->cmnd;
> > u16 boundary, len;
> > u64 lba, lba_tmp;
> > + bool meta_data_locked = false;
> > + bool lbp = scsi_debug_lbp();
> > int ret;
> > if (!scsi_debug_atomic_write()) {
> > @@ -6244,7 +6246,18 @@ static int resp_atomic_write(struct scsi_cmnd *scp,
> > }
> > }
> > + if (lbp) {
> > + sdeb_meta_write_lock(sip);
> > + meta_data_locked = true;
> > + }
> > +
> > ret = do_device_access(sip, scp, 0, lba, len, 0, true, true);
> > + if (unlikely(lbp))
> > + map_region(sip, lba, len);> +
> > + if (meta_data_locked)
>
> Do we really need meta_data_locked variable? why not:
> if (lbp)
> sdeb_meta_write_unlock(sip);
>
Yes, that would work for resp_atomic_write() as it does not support zones.
The code was cargo-culted from resp_write_dt0(), which does support zones.
Will fix in a v5. Will wait until Monday before I respin so that other
people (including Damien) get a chance to review v4.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-09-18 8:10 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
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 [this message]
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=aqzx1AUJExRHuz4S@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox