Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Damien Le Moal" <dlemoal@kernel.org>
Cc: dlemoal@kernel.org, linux-s390@vger.kernel.org,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	cassel@kernel.org,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v6 22/40] scsi: myrX: use 16-bits defined sense codes
Date: Tue, 08 Sep 2026 09:59:07 +0000	[thread overview]
Message-ID: <20260908095907.E80BC1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260908090308.1085097-23-dlemoal@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] The REQUEST_SENSE command intercepts the CDB but returns without calling scsi_done(), causing the command to hang.
--

commit b860b6810bf948611bc8eabd52fcae5e876d0483
Author: Damien Le Moal <dlemoal@kernel.org>
scsi: myrX: use 16-bits defined sense codes

Refactor the Mylex RAID controller driver to use scsi_set_sense() and the
16-bits sense_code field of struct scsi_sense_hdr and replace all
hard-coded additional sense codes and additional sense code qualifiers
with the enum values defined in include/scsi/scsi_sense.h.

> diff --git a/drivers/scsi/myrb.c b/drivers/scsi/myrb.c
> index 3678b66310ed0..95df6e5345f7a 100644
> --- a/drivers/scsi/myrb.c
> +++ b/drivers/scsi/myrb.c

[ ... ]

> @@ -1493,8 +1495,8 @@ static enum scsi_qc_status myrb_ldev_queuecommand(struct Scsi_Host *shost,
>  		return 0;

[Severity: High]
This is a pre-existing issue, but does this missing scsi_done() cause the
REQUEST_SENSE command to hang indefinitely?

Looking at myrb_ldev_queuecommand(), the REQUEST_SENSE command is intercepted
and returns without calling scsi_done():

	case REQUEST_SENSE:
		myrb_request_sense(cb, scmd);
		scmd->result = (DID_OK << 16);
		return 0;

Because this command is never completed, could it hang indefinitely and
eventually trigger the SCSI midlayer error handler?

Since userspace applications with access to the SCSI generic device
can send arbitrary SCSI commands via the SG_IO ioctl, could this be reached
from userspace and trigger a local denial of service by forcing SCSI error
recovery?

>  	case SEND_DIAGNOSTIC:
>  		if (scmd->cmnd[1] != 0x04) {
> -			/* Illegal request, invalid field in CDB */
> -			scsi_build_sense(scmd, 0, ILLEGAL_REQUEST, 0x24, 0);
> +			scsi_set_sense(scmd, 0, ILLEGAL_REQUEST,
> +				       INVALID_FIELD_IN_CDB);
>  		} else {
>  			/* Assume good status */
>  			scmd->result = (DID_OK << 16);

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

  reply	other threads:[~2026-09-08  9:59 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  9:02 [PATCH v6 00/40] Use defined 16-bits ASC/ASCQ combinations Damien Le Moal
2026-09-08  9:02 ` [PATCH v6 01/40] scsi: define all additional sense codes and their qualifiers Damien Le Moal
2026-09-08  9:39   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 02/40] scsi: constants: use defined sense codes Damien Le Moal
2026-09-08  9:12   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 03/40] scsi: constants: rename internal struct field names Damien Le Moal
2026-09-08  9:10   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 04/40] scsi: rename sense field of struct scsi_failure Damien Le Moal
2026-09-08  9:18   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 05/40] scsi: prepare for using 16-bits defined sense codes Damien Le Moal
2026-09-08  9:18   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 06/40] scsi: use struct scsi_sense_hdr to log sense keys and codes Damien Le Moal
2026-09-08  9:17   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 07/40] scsi: core: use 16-bits defined sense codes Damien Le Moal
2026-09-08  9:24   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 08/40] scsi: sd: " Damien Le Moal
2026-09-08  9:26   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 09/40] scsi: sr: " Damien Le Moal
2026-09-08  9:27   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 10/40] scsi: ses: " Damien Le Moal
2026-09-08  9:33   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 11/40] scsi: ch: " Damien Le Moal
2026-09-08  9:32   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 12/40] scsi: st: " Damien Le Moal
2026-09-08  9:33   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 13/40] scsi: device_handlers: hp_sw: " Damien Le Moal
2026-09-08  9:35   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 14/40] scsi: device_handlers: rdac: " Damien Le Moal
2026-09-08  9:37   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 15/40] scsi: device_handlers: emc: " Damien Le Moal
2026-09-08  9:37   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 16/40] scsi: device_handlers: alua: " Damien Le Moal
2026-09-08  9:43   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 17/40] scsi: mpt3sas: " Damien Le Moal
2026-09-08  9:48   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 18/40] scsi: mpi3mr: " Damien Le Moal
2026-09-08  9:42   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 19/40] scsi: 3w-xxxx: " Damien Le Moal
2026-09-08  9:51   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 20/40] scsi: leapraid: " Damien Le Moal
2026-09-08  9:50   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 21/40] scsi: megaraid: " Damien Le Moal
2026-09-08  9:48   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 22/40] scsi: myrX: " Damien Le Moal
2026-09-08  9:59   ` sashiko-bot [this message]
2026-09-08  9:02 ` [PATCH v6 23/40] scsi: smartpqi: " Damien Le Moal
2026-09-08  9:54   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 24/40] scsi: qla2xxx: " Damien Le Moal
2026-09-08  9:58   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 25/40] scsi: ps3rom: " Damien Le Moal
2026-09-08 10:05   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 26/40] scsi: lpfc: " Damien Le Moal
2026-09-08 10:03   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 27/40] scsi: stex: " Damien Le Moal
2026-09-08 10:14   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 28/40] scsi: mvumi: " Damien Le Moal
2026-09-08 10:12   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 29/40] scsi: libiscsi: " Damien Le Moal
2026-09-08 10:08   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 30/40] scsi: ibmvscsi_tgt: " Damien Le Moal
2026-09-08 10:18   ` sashiko-bot
2026-09-08  9:02 ` [PATCH v6 31/40] scsi: scsi_debug: " Damien Le Moal
2026-09-08 10:20   ` sashiko-bot
2026-09-08  9:03 ` [PATCH v6 32/40] scsi: hpsa: " Damien Le Moal
2026-09-08 10:19   ` sashiko-bot
2026-09-09 19:02   ` Don.Brace
2026-09-08  9:03 ` [PATCH v6 33/40] scsi: storvsc: " Damien Le Moal
2026-09-08 10:28   ` sashiko-bot
2026-09-08  9:03 ` [PATCH v6 34/40] target: " Damien Le Moal
2026-09-08 10:29   ` sashiko-bot
2026-09-08  9:03 ` [PATCH v6 35/40] usb: storage: " Damien Le Moal
2026-09-08 10:27   ` sashiko-bot
2026-09-08  9:03 ` [PATCH v6 36/40] cdrom: " Damien Le Moal
2026-09-08 10:24   ` sashiko-bot
2026-09-08  9:03 ` [PATCH v6 37/40] ata: libata: " Damien Le Moal
2026-09-08 10:33   ` sashiko-bot
2026-09-08  9:03 ` [PATCH v6 38/40] s390: scsi: " Damien Le Moal
2026-09-08 10:34   ` sashiko-bot
2026-09-08  9:03 ` [PATCH v6 39/40] scsi: cleanup scsi_proto.h Damien Le Moal
2026-09-08 10:36   ` sashiko-bot
2026-09-08  9:03 ` [PATCH v6 40/40] scsi: remove scsi_build_sense() and scsi_build_sense_buffer() Damien Le Moal
2026-09-08 10:32   ` 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=20260908095907.E80BC1F00A3A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox