From: Keith Busch <kbusch@kernel.org>
To: Martin George <martinus.gpy@gmail.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
hare@kernel.org, Martin George <marting@netapp.com>
Subject: Re: [PATCH] nvme-tcp: send only permitted commands for secure concat
Date: Mon, 15 Sep 2025 10:25:33 -0600 [thread overview]
Message-ID: <aMg9_TG8IG9jnbwv@kbusch-mbp> (raw)
In-Reply-To: <20250909103509.10343-1-marting@netapp.com>
On Tue, Sep 09, 2025 at 04:05:09PM +0530, Martin George wrote:
> In addition to sending permitted commands such as connect/auth
> over the initial unencrypted admin connection as part of secure
> channel concatenation, the host also sends commands such as
> Property Get and Identify on the same. This is a spec violation
> leading to secure concat failures. Fix this by ensuring these
> additional commands are avoided on this connection.
Thanks, applied to nvme-6.18.
prev parent reply other threads:[~2025-09-15 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 10:35 [PATCH] nvme-tcp: send only permitted commands for secure concat Martin George
2025-09-10 12:58 ` Hannes Reinecke
2025-09-11 13:07 ` Martin George
2025-09-15 15:58 ` Hannes Reinecke
2025-09-15 16:25 ` Keith Busch [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=aMg9_TG8IG9jnbwv@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hare@kernel.org \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=marting@netapp.com \
--cc=martinus.gpy@gmail.com \
--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