From: Laurence Oberman <loberman@redhat.com>
To: sashiko-reviews@lists.linux.dev, Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org, cassel@kernel.org
Subject: Re: [PATCH 12/37] scsi: st: use 16-bits defined sense codes
Date: Wed, 16 Sep 2026 11:29:34 -0400 [thread overview]
Message-ID: <2ff511fa29b801ab74ce9ee60e1257c47918c1db.camel@redhat.com> (raw)
In-Reply-To: <20260831021927.90FD21F00A3D@smtp.kernel.org>
On Mon, 2026-08-31 at 02:19 +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue(s) to consider:
> - [Medium] Incorrectly assigning ASC value to ASCQ in SCSI
> tracepoint.
> --
>
> commit c1f7c0aa9501c3562bd45de8a85431d940fa338b
> Author: Damien Le Moal <dlemoal@kernel.org>
> Subject: scsi: st: use 16-bits defined sense codes
>
> This commit refactors the SCSI tape driver to use the 16-bit
> sense_code
> field of struct scsi_sense_hdr. It replaces hard-coded additional
> sense
> codes and qualifiers with enum values defined in
> include/scsi/scsi_sense.h
> to improve code clarity.
>
> While reviewing this patch series, I noticed an issue introduced in
> the
> related change to include/trace/events/scsi.h:
>
> > diff --git a/include/trace/events/scsi.h
> > b/include/trace/events/scsi.h
> > --- a/include/trace/events/scsi.h
> > +++ b/include/trace/events/scsi.h
> > @@ -303,8 +303,8 @@
> > DECLARE_EVENT_CLASS(scsi_cmd_done_timeout_template,
> > if (cmd->sense_buffer && SCSI_SENSE_VALID(cmd) &&
> > scsi_command_normalize_sense(cmd, &sshdr)) {
> > __entry->sense_key = sshdr.sense_key;
> > - __entry->asc = sshdr.asc;
> > - __entry->ascq = sshdr.ascq;
> > + __entry->asc = scsi_sense_asc(&sshdr);
> > + __entry->ascq = scsi_sense_asc(&sshdr); <-
> > --- here
> ^^^^^^^^^^^^^^
>
> [Severity: Medium]
> Is there a typo in this assignment?
>
> In the scsi_cmd_done_timeout_template tracepoint, __entry->ascq is
> being
> assigned scsi_sense_asc(&sshdr) instead of the ASCQ value. This
> appears to
> log the Additional Sense Code for both the asc and ascq fields, which
> will
> result in lost diagnostic data when userspace tools analyze SCSI
> errors via
> tracepoints.
>
> Should this use scsi_sense_ascq(&sshdr) for the ascq field instead?
Hello Damien
This seems to be real issue here that sashiko found
We assign the same for __entry->ascq as we do for __entry->asc i.e.
scsi_sense_asc(&sshdr)
We need to have it as
+ __entry->asc = scsi_sense_asc(&sshdr);
+ __entry->ascq = scsi_sense_ascq(&sshdr); <--
Otherwise we will miss the ASCQ
Thanks
Laurence
next prev parent reply other threads:[~2026-09-16 15:29 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 2:04 [PATCH 00/37] Use defined 16-bits ASC/ASCQ combinations Damien Le Moal
2026-08-31 2:04 ` [PATCH 01/37] scsi: define all additional sense codes and their qualifiers Damien Le Moal
2026-08-31 2:04 ` [PATCH 02/37] scsi: constants: use defined sense codes Damien Le Moal
2026-08-31 2:04 ` [PATCH 03/37] scsi: constants: rename internal struct field names Damien Le Moal
2026-08-31 2:04 ` [PATCH 04/37] scsi: rename sense field of struct scsi_failure Damien Le Moal
2026-08-31 2:17 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 05/37] scsi: prepare for using 16-bits defined sense codes Damien Le Moal
2026-08-31 2:04 ` [PATCH 06/37] scsi: use struct scsi_sense_hdr to log sense keys and codes Damien Le Moal
2026-08-31 2:04 ` [PATCH 07/37] scsi: core: use 16-bits defined sense codes Damien Le Moal
2026-08-31 2:18 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 08/37] scsi: sd: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 09/37] scsi: sr: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 10/37] scsi: ses: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 11/37] scsi: ch: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 12/37] scsi: st: " Damien Le Moal
2026-08-31 2:19 ` sashiko-bot
2026-09-16 15:29 ` Laurence Oberman [this message]
2026-09-17 3:14 ` Damien Le Moal
2026-08-31 2:04 ` [PATCH 13/37] scsi: device_handlers: hp_sw: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 14/37] scsi: device_handlers: rdac: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 15/37] scsi: device_handlers: emc: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 16/37] scsi: device_handlers: alua: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 17/37] scsi: mpt3sas: " Damien Le Moal
2026-08-31 2:19 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 18/37] scsi: mpi3mr: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 19/37] scsi: 3w-xxxx: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 20/37] scsi: leapraid: " Damien Le Moal
2026-08-31 2:18 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 21/37] scsi: megaraid: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 22/37] scsi: myrX: " Damien Le Moal
2026-08-31 2:30 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 23/37] scsi: smartpqi: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 24/37] scsi: qla2xxx: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 25/37] scsi: ps3rom: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 26/37] scsi: lpfc: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 27/37] scsi: stex: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 28/37] scsi: mvumi: " Damien Le Moal
2026-08-31 2:24 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 29/37] scsi: libiscsi: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 30/37] scsi: ibmvscsi_tgt: " Damien Le Moal
2026-08-31 2:27 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 31/37] scsi: scsi_debug: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 32/37] scsi: hpsa: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 33/37] scsi: storvsc: " Damien Le Moal
2026-08-31 2:27 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 34/37] usb: storage: " Damien Le Moal
2026-08-31 2:04 ` [PATCH 35/37] cdrom: " Damien Le Moal
2026-08-31 2:29 ` sashiko-bot
2026-08-31 2:04 ` [PATCH 36/37] ata: libata: " Damien Le Moal
2026-09-02 11:29 ` Niklas Cassel
2026-09-02 23:48 ` Damien Le Moal
2026-08-31 2:04 ` [PATCH 37/37] scsi: cleanup scsi_proto.h Damien Le Moal
2026-08-31 2:31 ` sashiko-bot
2026-08-31 2:36 ` [PATCH 00/37] Use defined 16-bits ASC/ASCQ combinations 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=2ff511fa29b801ab74ce9ee60e1257c47918c1db.camel@redhat.com \
--to=loberman@redhat.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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