All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Damien Le Moal" <dlemoal@kernel.org>
Cc: "Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	linux-scsi@vger.kernel.org,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>,
	dlemoal@kernel.org, linux-ide@vger.kernel.org,
	linux-s390@vger.kernel.org, cassel@kernel.org
Subject: Re: [PATCH v3 08/40] scsi: sd: use 16-bits defined sense codes
Date: Fri, 04 Sep 2026 01:04:25 +0000	[thread overview]
Message-ID: <20260904010426.021131F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260904002644.157668-9-dlemoal@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Refactoring changes `sd_zbc_complete()` to strict ASC/ASCQ match instead of just ASC, unintentionally altering behavior.
--

commit 5c4223357b4b8d6bbeafe176fdc1d3eeb2183125
Author: Damien Le Moal <dlemoal@kernel.org>
Subject: scsi: sd: use 16-bits defined sense codes

This commit refactors the SCSI disk driver to use 16-bit sense codes where
possible, replacing hard-coded asc and ascq values with enums from
include/scsi/scsi_sense.h to improve code clarity.

> diff --git a/drivers/scsi/sd_zbc.c b/drivers/scsi/sd_zbc.c
> --- a/drivers/scsi/sd_zbc.c
> +++ b/drivers/scsi/sd_zbc.c
> @@ -369,7 +369,7 @@ unsigned int sd_zbc_complete(struct scsi_cmnd *cmd, unsigned int good_bytes,
>  	if (op_is_zone_mgmt(req_op(rq)) &&
>  	    result &&
>  	    sshdr->sense_key == ILLEGAL_REQUEST &&
> -	    sshdr->asc == 0x24) {
> +	    sshdr->sense_code == INVALID_FIELD_IN_CDB) {

[Severity: Medium]
Could this refactoring introduce a regression in error handling for
non-compliant or buggy devices?

The previous code checked only sshdr->asc == 0x24 (allowing any ascq),
whereas checking the 16-bit sshdr->sense_code against INVALID_FIELD_IN_CDB
requires an exact match where ascq is 0x00.

If a device returns an asc of 0x24 with a non-zero ascq for a zone
management command attempted on a conventional zone, the kernel will no
longer quiet the expected error with RQF_QUIET, potentially leading to
error log spam.

Since the commit message notes "No functional change intended", and other
parts of the patch (like in sd_done() in sd.c) deliberately preserve the
"any ascq" behavior by using scsi_sense_asc(sshdr) == ASC_INVALID_FIELD_IN_CDB,
should this code use scsi_sense_asc() here as well?

>  		/*
>  		 * INVALID FIELD IN CDB error: a zone management command was
>  		 * attempted on a conventional zone. Nothing to worry about,

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260904002644.157668-1-dlemoal@kernel.org?part=8

  reply	other threads:[~2026-09-04  1:04 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04  0:26 [PATCH v3 00/40] Use defined 16-bits ASC/ASCQ combinations Damien Le Moal
2026-09-04  0:26 ` [PATCH v3 01/40] scsi: define all additional sense codes and their qualifiers Damien Le Moal
2026-09-04  0:38   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 02/40] scsi: constants: use defined sense codes Damien Le Moal
2026-09-04  0:36   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 03/40] scsi: constants: rename internal struct field names Damien Le Moal
2026-09-04  0:38   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 04/40] scsi: rename sense field of struct scsi_failure Damien Le Moal
2026-09-04  0:43   ` sashiko-bot
2026-09-04 10:08   ` Johannes Thumshirn
2026-09-04  0:26 ` [PATCH v3 05/40] scsi: prepare for using 16-bits defined sense codes Damien Le Moal
2026-09-04  0:45   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 06/40] scsi: use struct scsi_sense_hdr to log sense keys and codes Damien Le Moal
2026-09-04  0:48   ` sashiko-bot
2026-09-04 10:11   ` Johannes Thumshirn
2026-09-04  0:26 ` [PATCH v3 07/40] scsi: core: use 16-bits defined sense codes Damien Le Moal
2026-09-04  0:53   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 08/40] scsi: sd: " Damien Le Moal
2026-09-04  1:04   ` sashiko-bot [this message]
2026-09-04  0:26 ` [PATCH v3 09/40] scsi: sr: " Damien Le Moal
2026-09-04  1:02   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 10/40] scsi: ses: " Damien Le Moal
2026-09-04  1:06   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 11/40] scsi: ch: " Damien Le Moal
2026-09-04  1:09   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 12/40] scsi: st: " Damien Le Moal
2026-09-04  1:11   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 13/40] scsi: device_handlers: hp_sw: " Damien Le Moal
2026-09-04  1:13   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 14/40] scsi: device_handlers: rdac: " Damien Le Moal
2026-09-04  1:15   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 15/40] scsi: device_handlers: emc: " Damien Le Moal
2026-09-04  1:20   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 16/40] scsi: device_handlers: alua: " Damien Le Moal
2026-09-04  1:27   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 17/40] scsi: mpt3sas: " Damien Le Moal
2026-09-04  1:26   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 18/40] scsi: mpi3mr: " Damien Le Moal
2026-09-04  1:32   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 19/40] scsi: 3w-xxxx: " Damien Le Moal
2026-09-04  1:33   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 20/40] scsi: leapraid: " Damien Le Moal
2026-09-04  1:39   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 21/40] scsi: megaraid: " Damien Le Moal
2026-09-04  1:42   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 22/40] scsi: myrX: " Damien Le Moal
2026-09-04  1:53   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 23/40] scsi: smartpqi: " Damien Le Moal
2026-09-04  1:48   ` sashiko-bot
2026-09-04 15:15   ` Don.Brace
2026-09-04  0:26 ` [PATCH v3 24/40] scsi: qla2xxx: " Damien Le Moal
2026-09-04  1:52   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 25/40] scsi: ps3rom: " Damien Le Moal
2026-09-04  2:00   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 26/40] scsi: lpfc: " Damien Le Moal
2026-09-04  2:00   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 27/40] scsi: stex: " Damien Le Moal
2026-09-04  2:08   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 28/40] scsi: mvumi: " Damien Le Moal
2026-09-04  2:12   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 29/40] scsi: libiscsi: " Damien Le Moal
2026-09-04  2:12   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 30/40] scsi: ibmvscsi_tgt: " Damien Le Moal
2026-09-04  2:20   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 31/40] scsi: scsi_debug: " Damien Le Moal
2026-09-04  2:23   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 32/40] scsi: hpsa: " Damien Le Moal
2026-09-04  2:27   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 33/40] scsi: storvsc: " Damien Le Moal
2026-09-04  2:41   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 34/40] target: " Damien Le Moal
2026-09-04  2:37   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 35/40] usb: storage: " Damien Le Moal
2026-09-04  2:43   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 36/40] cdrom: " Damien Le Moal
2026-09-04  2:46   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 37/40] ata: libata: " Damien Le Moal
2026-09-04  2:49   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 38/40] s390: scsi: " Damien Le Moal
2026-09-04  2:50   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 39/40] scsi: cleanup scsi_proto.h Damien Le Moal
2026-09-04  2:56   ` sashiko-bot
2026-09-04  0:26 ` [PATCH v3 40/40] scsi: remove scsi_build_sense() and scsi_build_sense_buffer() Damien Le Moal
2026-09-04  2:53   ` sashiko-bot

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=20260904010426.021131F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-s390@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 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.