From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: Allow sending of admin commands to inaccessible paths
Date: Wed, 4 Jun 2025 10:07:37 +0200 [thread overview]
Message-ID: <20250604080737.GA15609@lst.de> (raw)
In-Reply-To: <20250530120142.130469-1-hare@kernel.org>
On Fri, May 30, 2025 at 02:01:42PM +0200, Hannes Reinecke wrote:
> The NVMe Base Specification (Section 8.1.1.10) specifies that admin
> commands should not be affected by ANA states. So implement a function
> nvme_find_admin_path() to return the first non-disabled path irrespective
> of the ANA state.
Nothing in here explains why we'd want to support passthrough of admin
commans to inaccessible controllers. What problems does this solve to
justify all the extra code?
prev parent reply other threads:[~2025-06-04 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 12:01 [PATCH] nvme: Allow sending of admin commands to inaccessible paths Hannes Reinecke
2025-06-04 8:07 ` Christoph Hellwig [this message]
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=20250604080737.GA15609@lst.de \
--to=hch@lst.de \
--cc=hare@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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