From: Hannes Reinecke <hare@suse.com>
To: Bart Van Assche <bvanassche@acm.org>,
Christoph Hellwig <hch@infradead.org>,
Po-Wen Kao <powenkao@google.com>
Cc: "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"open list:SCSI SUBSYSTEM" <linux-scsi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] scsi: core: Fix error handler encryption support
Date: Thu, 4 Dec 2025 08:55:16 +0100 [thread overview]
Message-ID: <e792b704-6f06-47a9-82b1-af0e4a0da4d9@suse.com> (raw)
In-Reply-To: <88900700-7f37-4c3e-878e-cf5f68f006cc@acm.org>
On 12/3/25 16:55, Bart Van Assche wrote:
> On 12/2/25 10:42 PM, Hannes Reinecke wrote:
>> There had been an intersection with the reserved command stuff, but
>> now that Bart has dusted things off there I guess I should give it
>> another go.
>
> Does that patch series perhaps involve allocating a reserved command
> from inside the SCSI error handler? Won't that break SCSI LLDs that
> restrict the queue depth to one? I think that the following SCSI LLDs
> only support one command (.can_queue = 1):
reserved commands are only implemented for adapters which require an
LLD specific 'tag' to send TMFs (eg fnic, aacraid, or hpsa).
Most HBAs (especially the older ones) are not that elaborate, and
there TMFs are not commands per se but rather operations on the HBA.
EG fdomain host_reset is just settings some bits in some registers,
no command allocation needed at all.
So for those we don't need to allocate _any_ commands for TMFs,
consequently we don't need to implement reserved commands and
hence TMFs are not guarded by .can_queue at all.
> * drivers/scsi/fdomain.c
> * drivers/scsi/mac53c94.c
> * drivers/scsi/ppa.c
> * drivers/scsi/imm.c
> * drivers/scsi/aha152x.c
>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.com +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2025-12-04 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 7:33 [PATCH v2 1/1] scsi: core: Fix error handler encryption support Po-Wen Kao
2025-12-03 7:38 ` Christoph Hellwig
2025-12-03 8:42 ` Hannes Reinecke
2025-12-03 15:55 ` Bart Van Assche
2025-12-04 7:55 ` Hannes Reinecke [this message]
2025-12-03 15:57 ` Bart Van Assche
2025-12-04 10:13 ` Christoph Hellwig
2025-12-04 23:20 ` Brian Kao
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=e792b704-6f06-47a9-82b1-af0e4a0da4d9@suse.com \
--to=hare@suse.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=powenkao@google.com \
/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