From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: sashiko-reviews@lists.linux.dev, linux-ide@vger.kernel.org
Subject: Re: [PATCH v2 4/5] ata: libata-scsi: support reporting options 2 in REPORT SUPPORTED OPERATION CODES
Date: Thu, 2 Jul 2026 13:41:14 +0200 [thread overview]
Message-ID: <akZOWmrdZF8LrfEA@ryzen> (raw)
In-Reply-To: <3acde700-be7c-4ca0-b646-1dc5f6976cad@kernel.org>
On Thu, Jul 02, 2026 at 04:00:18PM +0900, Damien Le Moal wrote:
> > According to SPC-5, option 2 queries for unsupported commands (and similarly,
> > option 1 queries for commands with service actions) must return SUPPORT=001b.
> > Instead, this implementation erroneously aborts the command by calling
> > ata_scsi_set_invalid_field(), preventing the code from falling through and
> > correctly populating the response buffer.
>
> Sashiko, please reread the SPC specifications. It says:
>
> If the REQUESTED OPERATION CODE field specifies an operation code for
> which the device server does not implement service actions a, then the
> device server shall terminate the command with CHECK CONDITION
> status, with the sense key set to ILLEGAL REQUEST, and the additional
> sense code set to INVALID FIELD IN CDB.
>
> Which is exactly what we are testing here.
This is a bit funny :D
It would be nice if Sashiko actually listened (like a real AI agent),
re-read the spec, and updated posted an updated review comment :)
Perhaps try to include the SPC spec excerpt in the commit message for V3,
and see if that helps Sashiko parse the spec correctly ? :)
Kind regards,
Niklas
next prev parent reply other threads:[~2026-07-02 11:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 6:34 [PATCH v2 0/5] Improve ata_scsi_report_supported_opcodes() Damien Le Moal
2026-07-02 6:34 ` [PATCH v2 1/5] ata: libata: rename ata_dev_is_zac() Damien Le Moal
2026-07-02 6:38 ` Hannes Reinecke
2026-07-02 7:16 ` sashiko-bot
2026-07-02 6:34 ` [PATCH v2 2/5] ata: libata-scsi: refactor ata_scsi_report_supported_opcodes() Damien Le Moal
2026-07-02 6:44 ` Hannes Reinecke
2026-07-02 7:01 ` Damien Le Moal
2026-07-02 6:53 ` sashiko-bot
2026-07-02 13:25 ` Niklas Cassel
2026-07-02 14:36 ` Niklas Cassel
2026-07-02 14:48 ` Christoph Hellwig
2026-07-02 14:53 ` Niklas Cassel
2026-07-02 6:34 ` [PATCH v2 3/5] ata: libata-scsi: improve service action support in ata_scsi_report_supported_opcodes() Damien Le Moal
2026-07-02 6:45 ` Hannes Reinecke
2026-07-02 6:47 ` sashiko-bot
2026-07-02 6:34 ` [PATCH v2 4/5] ata: libata-scsi: support reporting options 2 in REPORT SUPPORTED OPERATION CODES Damien Le Moal
2026-07-02 6:46 ` Hannes Reinecke
2026-07-02 6:52 ` sashiko-bot
2026-07-02 7:00 ` Damien Le Moal
2026-07-02 11:41 ` Niklas Cassel [this message]
2026-07-02 6:53 ` Hannes Reinecke
2026-07-02 6:34 ` [PATCH v2 5/5] ata: libata-scsi: support the all command format for reporting supported commands Damien Le Moal
2026-07-02 6:54 ` Hannes Reinecke
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=akZOWmrdZF8LrfEA@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@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.