public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
	linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 14/16] nvmet: Allow to change 'TSAS' and 'TREQ'
Date: Tue,  8 Aug 2023 18:53:52 +0200	[thread overview]
Message-ID: <20230808165354.123499-15-hare@suse.de> (raw)
In-Reply-To: <20230808165354.123499-1-hare@suse.de>

Allow to change 'TSAS' and 'TREQ' to values specified in the spec.

Signed-off-by: Hannes Reinecke <hare@suse.de>
---
 drivers/nvme/target/configfs.c | 36 +++++++++++++++++++++++++++++++---
 1 file changed, 33 insertions(+), 3 deletions(-)

diff --git a/drivers/nvme/target/configfs.c b/drivers/nvme/target/configfs.c
index 7f826ac8b75c..3c2aeb763e22 100644
--- a/drivers/nvme/target/configfs.c
+++ b/drivers/nvme/target/configfs.c
@@ -159,10 +159,15 @@ static const struct nvmet_type_name_map nvmet_addr_treq[] = {
 	{ NVMF_TREQ_NOT_REQUIRED,	"not required" },
 };
 
+static inline u8 nvmet_port_treq(struct nvmet_port *port)
+{
+	return (port->disc_addr.treq & NVME_TREQ_SECURE_CHANNEL_MASK);
+}
+
 static ssize_t nvmet_addr_treq_show(struct config_item *item, char *page)
 {
-	u8 treq = to_nvmet_port(item)->disc_addr.treq &
-		NVME_TREQ_SECURE_CHANNEL_MASK;
+	struct nvmet_port *port = to_nvmet_port(item);
+	u8 treq = nvmet_port_treq(port);
 	int i;
 
 	for (i = 0; i < ARRAY_SIZE(nvmet_addr_treq); i++) {
@@ -174,11 +179,16 @@ static ssize_t nvmet_addr_treq_show(struct config_item *item, char *page)
 	return snprintf(page, PAGE_SIZE, "\n");
 }
 
+static inline u8 nvmet_port_treq_mask(struct nvmet_port *port)
+{
+	return (port->disc_addr.treq & ~NVME_TREQ_SECURE_CHANNEL_MASK);
+}
+
 static ssize_t nvmet_addr_treq_store(struct config_item *item,
 		const char *page, size_t count)
 {
 	struct nvmet_port *port = to_nvmet_port(item);
-	u8 treq = port->disc_addr.treq & ~NVME_TREQ_SECURE_CHANNEL_MASK;
+	u8 treq = nvmet_port_treq_mask(port);
 	int i;
 
 	if (nvmet_is_port_enabled(port, __func__))
@@ -193,6 +203,15 @@ static ssize_t nvmet_addr_treq_store(struct config_item *item,
 	return -EINVAL;
 
 found:
+	if (port->disc_addr.trtype == NVMF_TRTYPE_TCP) {
+		if (port->disc_addr.tsas.tcp.sectype != NVMF_TCP_SECTYPE_TLS13) {
+			pr_warn("cannot change TREQ when TLS is not enabled\n");
+			return -EINVAL;
+		} else if (nvmet_addr_treq[i].type == NVMF_TREQ_NOT_SPECIFIED) {
+			pr_warn("cannot set TREQ to 'not specified' when TLS is enabled\n");
+			return -EINVAL;
+		}
+	}
 	treq |= nvmet_addr_treq[i].type;
 	port->disc_addr.treq = treq;
 	return count;
@@ -371,6 +390,7 @@ static ssize_t nvmet_addr_tsas_store(struct config_item *item,
 		const char *page, size_t count)
 {
 	struct nvmet_port *port = to_nvmet_port(item);
+	u8 treq = nvmet_port_treq_mask(port);
 	int i;
 
 	if (nvmet_is_port_enabled(port, __func__))
@@ -389,6 +409,16 @@ static ssize_t nvmet_addr_tsas_store(struct config_item *item,
 
 found:
 	nvmet_port_init_tsas_tcp(port, nvmet_addr_tsas_tcp[i].type);
+	if (nvmet_addr_tsas_tcp[i].type == NVMF_TCP_SECTYPE_TLS13) {
+		if (nvmet_port_treq(port) == NVMF_TREQ_NOT_SPECIFIED)
+			treq |= NVMF_TREQ_REQUIRED;
+		else
+			treq |= nvmet_port_treq(port);
+	} else {
+		/* Set to 'not specified' if TLS is not enabled */
+		treq |= NVMF_TREQ_NOT_SPECIFIED;
+	}
+	port->disc_addr.treq = treq;
 	return count;
 }
 
-- 
2.35.3



  parent reply	other threads:[~2023-08-08 16:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08 16:53 [PATCHv6 00/16] nvme: In-kernel TLS support for TCP Hannes Reinecke
2023-08-08 16:53 ` [PATCH 01/16] nvme-keyring: register '.nvme' keyring Hannes Reinecke
2023-08-08 16:53 ` [PATCH 02/16] nvme-keyring: define a 'psk' keytype Hannes Reinecke
2023-08-08 16:53 ` [PATCH 03/16] nvme: add TCP TSAS definitions Hannes Reinecke
2023-08-08 16:53 ` [PATCH 04/16] nvme-tcp: add definitions for TLS cipher suites Hannes Reinecke
2023-08-08 16:53 ` [PATCH 05/16] nvme-keyring: implement nvme_tls_psk_default() Hannes Reinecke
2023-08-08 16:53 ` [PATCH 06/16] security/keys: export key_lookup() Hannes Reinecke
2023-08-10 13:41   ` David Howells
2023-08-08 16:53 ` [PATCH 07/16] nvme-tcp: allocate socket file Hannes Reinecke
2023-08-08 16:53 ` [PATCH 08/16] nvme-tcp: enable TLS handshake upcall Hannes Reinecke
2023-08-09  9:47   ` Sagi Grimberg
2023-08-09 10:00     ` Hannes Reinecke
2023-08-08 16:53 ` [PATCH 09/16] nvme-tcp: control message handling for recvmsg() Hannes Reinecke
2023-08-08 16:53 ` [PATCH 10/16] nvme-fabrics: parse options 'keyring' and 'tls_key' Hannes Reinecke
2023-08-09  9:56   ` Sagi Grimberg
2023-08-09 10:02     ` Hannes Reinecke
2023-08-08 16:53 ` [PATCH 11/16] nvmet: make TCP sectype settable via configfs Hannes Reinecke
2023-08-08 16:53 ` [PATCH 12/16] nvmet-tcp: make nvmet_tcp_alloc_queue() a void function Hannes Reinecke
2023-08-09 10:26   ` Sagi Grimberg
2023-08-08 16:53 ` [PATCH 13/16] nvmet-tcp: allocate socket file Hannes Reinecke
2023-08-09 10:28   ` Sagi Grimberg
2023-08-08 16:53 ` Hannes Reinecke [this message]
2023-08-09 10:44   ` [PATCH 14/16] nvmet: Allow to change 'TSAS' and 'TREQ' Sagi Grimberg
2023-08-09 11:18     ` Hannes Reinecke
2023-08-08 16:53 ` [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall Hannes Reinecke
2023-08-09 10:51   ` Sagi Grimberg
2023-08-09 11:33     ` Hannes Reinecke
2023-08-09 12:51       ` Sagi Grimberg
2023-08-09 12:54         ` Sagi Grimberg
2023-08-09 13:24           ` Hannes Reinecke
2023-08-09 13:22         ` Hannes Reinecke
2023-08-10  7:09     ` Hannes Reinecke
2023-08-10  8:04       ` Sagi Grimberg
2023-08-08 16:53 ` [PATCH 16/16] nvmet-tcp: control messages for recvmsg() Hannes Reinecke
2023-08-09 11:30   ` Sagi Grimberg
2023-08-09 11:35     ` 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=20230808165354.123499-15-hare@suse.de \
    --to=hare@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox