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 v5 09/10] scsi: scsi_debug: Map the region written by WRITE ATOMIC (16)
Date: Thu, 24 Sep 2026 13:10:10 +0200 [thread overview]
Message-ID: <arUFEnJj0BX_gFQW@ryzen> (raw)
In-Reply-To: <3049af11-b93e-4849-8cf6-463a27792ae5@linux.dev>
Hello John,
On Mon, Sep 21, 2026 at 04:50:31PM +0100, John Garry wrote:
> On 9/21/26 16:40, Niklas Cassel wrote:
> > @@ -6246,7 +6247,16 @@ static int resp_atomic_write(struct scsi_cmnd *scp,
> > }
> > }
> > + if (lbp)
> > + sdeb_meta_write_lock(sip);
> > +
> > ret = do_device_access(sip, scp, 0, lba, len, 0, true, true);
> > + if (unlikely(lbp))
>
> Is this supposed to be called if ret <= 0?
>
> > + map_region(sip, lba, len);
> > +
> > + if (lbp)
It does not have to be skipped: SBC-6 4.7.4.6.2 allows a device to map a
deallocated LBA at any time, and resp_write_dt0() and resp_write_scat()
also call map_region() without looking at the result, so I will keep it
unconditional.
Looking at this, I did however find another bug in resp_atomic_write().
While scsi_debug does fail a short WRITE ATOMIC (16) with DID_ERROR,
a short write will currently modify the logical blocks up to the short
write. I will add a fix for this in my series.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-09-24 11:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 15:40 [PATCH v5 00/10] scsi: scsi_debug: fix zoned write validation Niklas Cassel
2026-09-21 15:40 ` [PATCH v5 01/10] scsi: scsi_debug: Refuse a zoned device with a non-zero lowest aligned LBA Niklas Cassel
2026-09-21 15:40 ` [PATCH v5 02/10] scsi: scsi_debug: Make atomic writes and ZBC emulation mutually exclusive Niklas Cassel
2026-09-21 15:40 ` [PATCH v5 03/10] scsi: scsi_debug: Take the zone metadata lock before the data lock Niklas Cassel
2026-09-21 15:40 ` [PATCH v5 04/10] scsi: scsi_debug: Evaluate scsi_debug_lbp() only once Niklas Cassel
2026-09-21 15:53 ` John Garry
2026-09-23 9:54 ` Johannes Thumshirn
2026-09-21 15:40 ` [PATCH v5 05/10] scsi: scsi_debug: Report the residual of a write Niklas Cassel
2026-09-21 15:40 ` [PATCH v5 06/10] scsi: scsi_debug: Enforce physical block alignment of zoned writes Niklas Cassel
2026-09-21 15:40 ` [PATCH v5 07/10] scsi: scsi_debug: Do not write a partial physical block to a zoned device Niklas Cassel
2026-09-21 15:40 ` [PATCH v5 08/10] scsi: scsi_debug: Advance the write pointer over the data written Niklas Cassel
2026-09-21 15:40 ` [PATCH v5 09/10] scsi: scsi_debug: Map the region written by WRITE ATOMIC (16) Niklas Cassel
2026-09-21 15:50 ` John Garry
2026-09-24 11:10 ` Niklas Cassel [this message]
2026-09-25 9:32 ` John Garry
2026-09-21 15:40 ` [PATCH v5 10/10] scsi: scsi_debug: Validate the access parameters of " Niklas Cassel
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=arUFEnJj0BX_gFQW@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