[PATCH v2] nvme: reserve a keep-alive admin tag for all transports

[Chao S]

On Thu, May 21, 2026, Christoph Hellwig wrote:
> True.  So maybe start filtering out all these things will go wrong
> commands.  Chao, can you start on that for keep alive?  We can then
> extend it as needed.

Sure, thank you so much for your help and comments!
Done.  v3 adds the filter (nvme_passthru_cmd_allowed) in the
passthrough path, rejecting KATO Set Features on non-fabrics with
-EOPNOTSUPP, and is structured to extend to other features later.
The reserve-a-tag change from v1/v2 is dropped.

For the blktests testcase you asked about earlier: I will send that
separately against the blktests tree.

Sent as a new series:
  https://lore.kernel.org/linux-nvme/20260522152807.2061501-1-coshi036@gmail.com/

Chao

On Fri, May 22, 2026 at 8:14 AM Christoph Hellwig <hch at lst.de> wrote:
>
> On Thu, May 21, 2026 at 08:38:29AM -0600, Keith Busch wrote:
> > This command is already special since we filter for it on the completion
> > side. We may want to selectively filter other Set Feature commands too.
> > For example, we don't want user space turning on Host Dispersed
> > Namespace Support, because this driver is not going to correctly react
> > to that one either.
>
> True.  So maybe start filtering out all these things will go wrong
> commands.  Chao, can you start on that for keep alive?  We can then
> extend it as needed.