From: Hannes Reinecke <hare@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@kernel.org>
Subject: [PATCH 0/2] nvme: restrict authentication to the admin queue
Date: Wed, 17 Jul 2024 13:03:36 +0200 [thread overview]
Message-ID: <20240717110338.27332-1-hare@kernel.org> (raw)
Hi all,
it might be an idea to restrict authentication to the admin queue only,
as authentication on I/O queues brings only so much additional benefit,
and the entire authentication is noticeably faster.
This patchsets enables the host to handle this situation, and adds a
new configfs entry 'dhchap_admin_only' for the target to enable this
behaviour.
Patches are on top of my 'secure-concat.v5' branch on kernel.org.
As usual, comments and reviews are welcome.
Hannes Reinecke (2):
nvme: Do not re-authenticate queues with no prior authentication
nvmet: Implement 'admin_only' authentication
drivers/nvme/host/auth.c | 17 ++++++++++++++++-
drivers/nvme/target/auth.c | 11 +++++++----
drivers/nvme/target/configfs.c | 24 ++++++++++++++++++++++++
drivers/nvme/target/fabrics-cmd-auth.c | 7 +++++++
drivers/nvme/target/fabrics-cmd.c | 7 +++++--
drivers/nvme/target/nvmet.h | 2 ++
6 files changed, 61 insertions(+), 7 deletions(-)
--
2.35.3
next reply other threads:[~2024-07-17 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 11:03 Hannes Reinecke [this message]
2024-07-17 11:03 ` [PATCH 1/2] nvme: Do not re-authenticate queues with no prior authentication Hannes Reinecke
2024-07-17 11:03 ` [PATCH 2/2] nvmet: Implement 'admin_only' authentication Hannes Reinecke
2024-07-17 22:40 ` Sagi Grimberg
2024-07-18 7:38 ` Hannes Reinecke
2024-07-21 11:32 ` Sagi Grimberg
2024-08-20 14:06 ` [PATCH 0/2] nvme: restrict authentication to the admin queue 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=20240717110338.27332-1-hare@kernel.org \
--to=hare@kernel.org \
--cc=hch@lst.de \
--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 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.