nvme: In-kernel TLS support for TCP
Subsystems (4)
v6 cover nvme: In-kernel TLS support for TCP
Hi all,
with the merge of Chuck Levers handshake upcall mechanism and my tls_read_sock() implementation finally merged with net-next it's now time to restart on the actual issue, namely implementing in-kernel TLS support for nvme-tcp.
The patchset is based on the recent net-next git tree; everything after commit 05191d8896b4 ("Merge branch 'in-kernel-support-for-the-tls-alert-protocol'") should work. Just a tiny wee snag has been discovered in the ->read_sock() implementation, so please ensure to have the patch 'net/tls: avoid TCP window full during ->read_sock()' merged, too.
It also requires the 'tlshd' userspace daemon
(https://github.com/oracle/ktls-utils)
for the actual TLS handshake.
Changes for nvme-cli are already included in the upstream repository.
Theory of operation:
A dedicated '.nvme' keyring is created to hold the pre-shared keys (PSKs) for the TLS handshake. Keys will have to be provisioned before TLS handshake is attempted; that can be done with the 'nvme gen-tls-key' command for nvme-cli (patches are already merged upstream).
After connection to the remote TCP port the client side will use the 'best' PSK (as inferred from the NVMe TCP spec) or the PSK specified by the '--tls_key' option to nvme-cli and call the TLS userspace daemon to initiate a TLS handshake.
The server side will then invoke the TLS userspace daemon to run the TLS handshake.
If the TLS handshake succeeds the userspace daemon will be activating kTLS on the socket, and control is passed back to the kernel.
This implementation currently does not implement the so-called 'secure concatenation' mode from NVMe-TCP; a TPAR is still pending with fixes for it, so I'll wait until it's published before posting patches for that.
Patchset can be found at:
git.kernel.org/pub/scm/linux/kernel/git/hare/nvme.git branch tls.v9
For testing I'm using this script, running on a nvme target with NQN 'nqn.test' and using 127.0.0.1 as a port:
modprobe nvmet-tcp
nvmetcli restore
modprobe nvme-tcp
./nvme gen-tls-key --subsysnqn=nqn.test -i
./nvme gen-tls-key --subsysnqn=nqn.2014-08.org.nvmexpress.discovery -i tlshd -c /etc/tlshd.conf
and then one can do a simple:
# nvme connect -t tcp -a 127.0.0.1 -s 4420 -n nqn.test --tls to start the connection.
As usual, comments and reviews are welcome.
Changes to v5:
- Include reviews from Sagi
- Split off nvmet tsas/treq handling
- Sanitize sock_file handling
Changes to v4:
- Split off network patches into a separate
patchset
- Handle TLS Alert notifications
Changes to v3:
- Really handle MSG_EOR for TLS
- Fixup MSG_SENDPAGE_NOTLAST handling
- Conditionally disable fabric option
Changes to v2:
- Included reviews from Sagi
- Removed MSG_SENDPAGE_NOTLAST
- Improved MSG_EOR handling for TLS
- Add config options NVME_TCP_TLS
and NVME_TARGET_TCP_TLS
Changes to the original RFC:
- Add a CONFIG_NVME_TLS config option
- Use a single PSK for the TLS handshake
- Make TLS connections mandatory
- Do not peek messages for the server
- Simplify data_ready callback
- Implement read_sock() for TLS
Hannes Reinecke (16):
nvme-keyring: register '.nvme' keyring
nvme-keyring: define a 'psk' keytype
nvme: add TCP TSAS definitions
nvme-tcp: add definitions for TLS cipher suites
nvme-keyring: implement nvme_tls_psk_default() security/keys: export key_lookup()
nvme-tcp: allocate socket file
nvme-tcp: enable TLS handshake upcall
nvme-tcp: control message handling for recvmsg()
nvme-fabrics: parse options 'keyring' and 'tls_key'
nvmet: make TCP sectype settable via configfs
nvmet-tcp: make nvmet_tcp_alloc_queue() a void function
nvmet-tcp: allocate socket file
nvmet: Allow to change 'TSAS' and 'TREQ'
nvmet-tcp: enable TLS handshake upcall
nvmet-tcp: control messages for recvmsg()
drivers/nvme/common/Kconfig | 4 + drivers/nvme/common/Makefile | 3 +- drivers/nvme/common/keyring.c | 182 +++++++++++++++++++++++++ drivers/nvme/host/Kconfig | 15 +++ drivers/nvme/host/core.c | 12 +- drivers/nvme/host/fabrics.c | 83 +++++++++++- drivers/nvme/host/fabrics.h | 9 ++ drivers/nvme/host/nvme.h | 1 + drivers/nvme/host/sysfs.c | 21 +++ drivers/nvme/host/tcp.c | 177 ++++++++++++++++++++++-- drivers/nvme/target/Kconfig | 15 +++ drivers/nvme/target/configfs.c | 128 +++++++++++++++++- drivers/nvme/target/nvmet.h | 1 + drivers/nvme/target/tcp.c | 238 +++++++++++++++++++++++++++++---- include/linux/nvme-keyring.h | 36 +++++ include/linux/nvme-tcp.h | 6 + include/linux/nvme.h | 10 ++ security/keys/key.c | 1 + 18 files changed, 897 insertions(+), 45 deletions(-) create mode 100644 drivers/nvme/common/keyring.c create mode 100644 include/linux/nvme-keyring.h
Signature · 1 line
2.35.3
PATCH v6 1/16 nvme-keyring: register '.nvme' keyring
Register a '.nvme' keyring to hold keys for TLS and DH-HMAC-CHAP and add a new config option NVME_KEYRING.
We need a separate keyring for NVMe as the configuration is done via individual commands (eg for configfs), and the usual per-session or per-process keyrings can't be used.
--- drivers/nvme/common/Kconfig | 4 ++++ drivers/nvme/common/Makefile | 3 ++- drivers/nvme/common/keyring.c | 40 +++++++++++++++++++++++++++++++++++ drivers/nvme/host/core.c | 10 +++++++-- include/linux/nvme-keyring.h | 28 ++++++++++++++++++++++++ 5 files changed, 82 insertions(+), 3 deletions(-) create mode 100644 drivers/nvme/common/keyring.c create mode 100644 include/linux/nvme-keyring.h
drivers/nvme/common/Kconfig +4 -0
@@ -2,3 +2,7 @@ config NVME_COMMON tristate + +config NVME_KEYRING + bool + select KEYS
drivers/nvme/common/Makefile +2 -1
@@ -4,4 +4,5 @@ ccflags-y += -I$(src) obj-$(CONFIG_NVME_COMMON) += nvme-common.o -nvme-common-y += auth.o +nvme-common-$(CONFIG_NVME_AUTH) += auth.o +nvme-common-$(CONFIG_NVME_KEYRING) += keyring.o
drivers/nvme/common/keyring.c new file +40 -0
@@ -0,0 +1,40 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* Copyright (c) 2023 Hannes Reinecke, SUSE Labs +*/ + +#include <linux/module.h> +#include <linux/seq_file.h> +#include <linux/key-type.h> +#include <keys/user-type.h> +#include <linux/nvme.h> + +static struct key *nvme_keyring; + +key_serial_t nvme_keyring_id (void ) +{ +return nvme_keyring->serial; +} +EXPORT_SYMBOL_GPL (nvme_keyring_id); + +int nvme_keyring_init (void ) +{ + nvme_keyring =keyring_alloc (".nvme" , +GLOBAL_ROOT_UID ,GLOBAL_ROOT_GID , +current_cred (), + (KEY_POS_ALL & ~KEY_POS_SETATTR ) | + (KEY_USR_ALL & ~KEY_USR_SETATTR ), +KEY_ALLOC_NOT_IN_QUOTA ,NULL ,NULL ); +if (IS_ERR (nvme_keyring)) +return PTR_ERR (nvme_keyring); + +return 0 ; +} +EXPORT_SYMBOL_GPL (nvme_keyring_init); + +void nvme_keyring_exit (void ) +{ +key_revoke (nvme_keyring); +key_put (nvme_keyring); +} +EXPORT_SYMBOL_GPL (nvme_keyring_exit);
drivers/nvme/host/core.c +8 -2
@@ -25,6 +25,7 @@#include "nvme.h" #include "fabrics.h" #include <linux/nvme-auth.h> +#include <linux/nvme-keyring.h> #define CREATE_TRACE_POINTS #include "trace.h"
@@ -4703,12 +4704,16 @@ static int __init nvme_core_init(void) result =PTR_ERR (nvme_ns_chr_class); goto unregister_generic_ns; } - - result =nvme_init_auth (); + result =nvme_keyring_init ();if (result) goto destroy_ns_chr; + result =nvme_init_auth (); +if (result) + goto keyring_exit;return 0 ; +keyring_exit: +nvme_keyring_exit (); destroy_ns_chr:class_destroy (nvme_ns_chr_class); unregister_generic_ns:
@@ -4732,6 +4737,7 @@ static int __init nvme_core_init(void) static void __exit nvme_core_exit(void) {nvme_exit_auth (); +nvme_keyring_exit ();class_destroy (nvme_ns_chr_class);class_destroy (nvme_subsys_class);class_destroy (nvme_class);
include/linux/nvme-keyring.h new file +28 -0
@@ -0,0 +1,28 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* Copyright (c) 2023 Hannes Reinecke, SUSE Labs +*/ + +#ifndef _NVME_KEYRING_H +#define _NVME_KEYRING_H + +#ifdef CONFIG_NVME_KEYRING + +key_serial_t nvme_keyring_id (void ); +int nvme_keyring_init (void ); +void nvme_keyring_exit (void ); + +#else + +static inline key_serial_t nvme_keyring_id (void ) +{ +return 0 ; +} +static inline int nvme_keyring_init (void ) +{ +return 0 ; +} +static inline void nvme_keyring_exit (void ) {} + +#endif /* !CONFIG_NVME_KEYRING */ +#endif /* _NVME_KEYRING_H */
Signature · 1 line
2.35.3
PATCH v6 2/16 nvme-keyring: define a 'psk' keytype
In reply to Hannes ReineckeDefine a 'psk' keytype to hold the NVMe TLS PSKs.
--- drivers/nvme/common/keyring.c | 94 +++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+)
drivers/nvme/common/keyring.c +94 -0
@@ -8,6 +8,8 @@#include <linux/key-type.h> #include <keys/user-type.h> #include <linux/nvme.h> +#include <linux/nvme-tcp.h> +#include <linux/nvme-keyring.h> static struct key *nvme_keyring;
@@ -17,8 +19,94 @@ key_serial_t nvme_keyring_id(void) }EXPORT_SYMBOL_GPL (nvme_keyring_id); +static void nvme_tls_psk_describe (const struct key *key,struct seq_file *m) +{ +seq_puts (m, key->description); +seq_printf (m,": %u" , key->datalen); +} + +static bool nvme_tls_psk_match (const struct key *key, +const struct key_match_data *match_data) +{ +const char *match_id; +size_t match_len; + +if (!key->description) { +pr_debug ("%s: no key description\n" , __func__); +return false; + } + match_len =strlen (key->description); +pr_debug ("%s: id %s len %zd\n" , __func__, key->description, match_len); + +if (!match_data->raw_data) { +pr_debug ("%s: no match data\n" , __func__); +return false; + } + match_id = match_data->raw_data; +pr_debug ("%s: match '%s' '%s' len %zd\n" , + __func__, match_id, key->description, match_len); +return !memcmp (key->description, match_id, match_len); +} + +static int nvme_tls_psk_match_preparse (struct key_match_data *match_data) +{ + match_data->lookup_type =KEYRING_SEARCH_LOOKUP_ITERATE ; + match_data->cmp = nvme_tls_psk_match; +return 0 ; +} + +static struct key_type nvme_tls_psk_key_type = { + .name ="psk" , + .flags =KEY_TYPE_NET_DOMAIN , + .preparse = user_preparse, + .free_preparse = user_free_preparse, + .match_preparse = nvme_tls_psk_match_preparse, + .instantiate = generic_key_instantiate, + .revoke = user_revoke, + .destroy = user_destroy, + .describe = nvme_tls_psk_describe, + .read = user_read, +}; + +static struct key *nvme_tls_psk_lookup (struct key *keyring, +const char *hostnqn,const char *subnqn, +int hmac,bool generated) +{ +char *identity; +size_t identity_len = (NVMF_NQN_SIZE ) *2 +11 ; +key_ref_t keyref; +key_serial_t keyring_id; + + identity =kzalloc (identity_len,GFP_KERNEL ); +if (!identity) +return ERR_PTR (-ENOMEM ); + +snprintf (identity, identity_len,"NVMe0%c%02d %s %s" , + generated ?'G' :'R' , hmac, hostnqn, subnqn); + +if (!keyring) + keyring = nvme_keyring; + keyring_id =key_serial (keyring); +pr_debug ("keyring %x lookup tls psk '%s'\n" , + keyring_id, identity); + keyref =keyring_search (make_key_ref (keyring, true), + &nvme_tls_psk_key_type, + identity, false); +if (IS_ERR (keyref)) { +pr_debug ("lookup tls psk '%s' failed, error %ld\n" , + identity,PTR_ERR (keyref)); +kfree (identity); +return ERR_PTR (-ENOKEY ); + } +kfree (identity); + +return key_ref_to_ptr (keyref); +} +int nvme_keyring_init (void ) { +int err; + nvme_keyring = keyring_alloc(".nvme", GLOBAL_ROOT_UID, GLOBAL_ROOT_GID, current_cred(),
@@ -28,12 +116,18 @@ int nvme_keyring_init(void)if (IS_ERR (nvme_keyring))return PTR_ERR (nvme_keyring); + err =register_key_type (&nvme_tls_psk_key_type); +if (err) { +key_put (nvme_keyring); +return err; + }return 0 ; }EXPORT_SYMBOL_GPL (nvme_keyring_init);void nvme_keyring_exit (void ) { +unregister_key_type (&nvme_tls_psk_key_type);key_revoke (nvme_keyring);key_put (nvme_keyring); }
Signature · 1 line
2.35.3
PATCH v6 3/16 nvme: add TCP TSAS definitions
In reply to Hannes Reinecke--- include/linux/nvme.h | 10 ++++++++++ 1 file changed, 10 insertions(+)
include/linux/nvme.h +10 -0
@@ -108,6 +108,13 @@ enum { NVMF_RDMA_CMS_RDMA_CM = 1, /* Sockets based endpoint addressing */ }; +/* TSAS SECTYPE for TCP transport */ +enum { +NVMF_TCP_SECTYPE_NONE =0 ,/* No Security */ +NVMF_TCP_SECTYPE_TLS12 =1 ,/* TLSv1.2, NVMe-oF 1.1 and NVMe-TCP 3.6.1.1 */ +NVMF_TCP_SECTYPE_TLS13 =2 ,/* TLSv1.3, NVMe-oF 1.1 and NVMe-TCP 3.6.1.1 */ +}; +#define NVME_AQ_DEPTH 32#define NVME_NR_AEN_COMMANDS 1#define NVME_AQ_BLK_MQ_DEPTH (NVME_AQ_DEPTH - NVME_NR_AEN_COMMANDS)
@@ -1493,6 +1500,9 @@ struct nvmf_disc_rsp_page_entry {__u16 pkey;__u8 resv10[246 ]; } rdma; +struct tcp { +__u8 sectype; + } tcp; } tsas; };
Signature · 1 line
2.35.3
PATCH v6 4/16 nvme-tcp: add definitions for TLS cipher suites
In reply to Hannes Reinecke--- include/linux/nvme-tcp.h | 6 ++++++ 1 file changed, 6 insertions(+)
include/linux/nvme-tcp.h +6 -0
@@ -18,6 +18,12 @@ enum nvme_tcp_pfv { NVME_TCP_PFV_1_0 = 0x0, }; +enum nvme_tcp_tls_cipher { +NVME_TCP_TLS_CIPHER_INVALID =0 , +NVME_TCP_TLS_CIPHER_SHA256 =1 , +NVME_TCP_TLS_CIPHER_SHA384 =2 , +}; +enum nvme_tcp_fatal_error_status {NVME_TCP_FES_INVALID_PDU_HDR =0x01 ,NVME_TCP_FES_PDU_SEQ_ERR =0x02 ,
Signature · 1 line
2.35.3
PATCH v6 5/16 nvme-keyring: implement nvme_tls_psk_default()
In reply to Hannes ReineckeImplement a function to select the preferred PSK for TLS. A 'retained' PSK should be preferred over a 'generated' PSK, and SHA-384 should be preferred to SHA-256.
--- drivers/nvme/common/keyring.c | 48 +++++++++++++++++++++++++++++++++++ include/linux/nvme-keyring.h | 8 ++++++ 2 files changed, 56 insertions(+)
drivers/nvme/common/keyring.c +48 -0
@@ -5,6 +5,7 @@#include <linux/module.h> #include <linux/seq_file.h> +#include <linux/key.h> #include <linux/key-type.h> #include <keys/user-type.h> #include <linux/nvme.h>
@@ -103,6 +104,53 @@ static struct key *nvme_tls_psk_lookup(struct key *keyring,return key_ref_to_ptr (keyref); } +/* +* NVMe PSK priority list +* +* 'Retained' PSKs (ie 'generated == false') +* should be preferred to 'generated' PSKs, +* and SHA-384 should be preferred to SHA-256. +*/ +struct nvme_tls_psk_priority_list { +bool generated; +enum nvme_tcp_tls_cipher cipher; +} nvme_tls_psk_prio[] = { + { .generated = false, + .cipher =NVME_TCP_TLS_CIPHER_SHA384 , }, + { .generated = false, + .cipher =NVME_TCP_TLS_CIPHER_SHA256 , }, + { .generated = true, + .cipher =NVME_TCP_TLS_CIPHER_SHA384 , }, + { .generated = true, + .cipher =NVME_TCP_TLS_CIPHER_SHA256 , }, +}; + +/* +* nvme_tls_psk_default - Return the preferred PSK to use for TLS ClientHello +*/ +key_serial_t nvme_tls_psk_default (struct key *keyring, +const char *hostnqn,const char *subnqn) +{ +struct key *tls_key; +key_serial_t tls_key_id; +int prio; + +for (prio =0 ; prio <ARRAY_SIZE (nvme_tls_psk_prio); prio++) { +bool generated = nvme_tls_psk_prio[prio].generated; +enum nvme_tcp_tls_cipher cipher = nvme_tls_psk_prio[prio].cipher; + + tls_key =nvme_tls_psk_lookup (keyring, hostnqn, subnqn, + cipher, generated); +if (!IS_ERR (tls_key)) { + tls_key_id = tls_key->serial; +key_put (tls_key); +return tls_key_id; + } + } +return 0 ; +} +EXPORT_SYMBOL_GPL (nvme_tls_psk_default); +int nvme_keyring_init (void ) {int err;
include/linux/nvme-keyring.h +8 -0
@@ -8,12 +8,20 @@#ifdef CONFIG_NVME_KEYRING +key_serial_t nvme_tls_psk_default (struct key *keyring, +const char *hostnqn,const char *subnqn); +key_serial_t nvme_keyring_id (void );int nvme_keyring_init (void );void nvme_keyring_exit (void );#else +static inline key_serial_t nvme_tls_psk_default (struct key *keyring, +const char *hostnqn,const char *subnqn) +{ +return 0 ; +}static inline key_serial_t nvme_keyring_id (void ) {return 0 ;
Signature · 1 line
2.35.3
PATCH v6 6/16 security/keys: export key_lookup()
In reply to Hannes ReineckeFor in-kernel consumers one cannot readily assign a user (eg when running from a workqueue), so the normal key search permissions cannot be applied.
This patch exports the 'key_lookup()' function for a simple lookup of keys without checking for permissions.
--- security/keys/key.c | 1 + 1 file changed, 1 insertion(+)
security/keys/key.c +1 -0
@@ -693,6 +693,7 @@ struct key *key_lookup(key_serial_t id)spin_unlock (&key_serial_lock);return key; } +EXPORT_SYMBOL_GPL (key_lookup);/* * Find and lock the specified key type against removal.
Signature · 1 line
2.35.3
Re: [PATCH 06/16] security/keys: export key_lookup()
Quoted 11 lines · Hannes Reinecke
For in-kernel consumers one cannot readily assign a user (eg when running from a workqueue), so the normal key search permissions cannot be applied.
This patch exports the 'key_lookup()' function for a simple lookup of keys without checking for permissions.Cc David Howells <[email protected]>Signed-off-by Hannes Reinecke <[email protected]>Reviewed-by Sagi Grimberg <[email protected]>...
+EXPORT_SYMBOL_GPL(key_lookup);
EXPORT_SYMBOL() please.
Otherwise:
PATCH v6 7/16 nvme-tcp: allocate socket file
In reply to Hannes ReineckeWhen using the TLS upcall we need to allocate a socket file such that the userspace daemon is able to use the socket.
--- drivers/nvme/host/tcp.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)
drivers/nvme/host/tcp.c +13 -2
@@ -1338,7 +1338,9 @@ static void nvme_tcp_free_queue(struct nvme_ctrl *nctrl, int qid) } noreclaim_flag =memalloc_noreclaim_save (); -sock_release (queue->sock); +/* ->sock will be released by fput() */ +fput (queue->sock->file); + queue->sock =NULL ;memalloc_noreclaim_restore (noreclaim_flag);kfree (queue->pdu);
@@ -1512,6 +1514,7 @@ static int nvme_tcp_alloc_queue(struct nvme_ctrl *nctrl, int qid)struct nvme_tcp_ctrl *ctrl =to_tcp_ctrl (nctrl);struct nvme_tcp_queue *queue = &ctrl->queues[qid];int ret, rcv_pdu_size; +struct file *sock_file;mutex_init (&queue->queue_lock); queue->ctrl = ctrl;
@@ -1534,6 +1537,13 @@ static int nvme_tcp_alloc_queue(struct nvme_ctrl *nctrl, int qid) goto err_destroy_mutex; } + sock_file =sock_alloc_file (queue->sock,O_CLOEXEC ,NULL ); +if (IS_ERR (sock_file)) { +sock_release (queue->sock); + queue->sock =NULL ; + ret =PTR_ERR (sock_file); + goto err_destroy_mutex; + }nvme_tcp_reclassify_socket (queue->sock);/* Single syn retry */
@@ -1640,7 +1650,8 @@ static int nvme_tcp_alloc_queue(struct nvme_ctrl *nctrl, int qid)if (queue->hdr_digest || queue->data_digest)nvme_tcp_free_crypto (queue); err_sock: -sock_release (queue->sock); +/* ->sock will be released by fput() */ +fput (queue->sock->file); queue->sock =NULL ; err_destroy_mutex:mutex_destroy (&queue->send_mutex);
Signature · 1 line
2.35.3
PATCH v6 8/16 nvme-tcp: enable TLS handshake upcall
In reply to Hannes ReineckeAdd a fabrics option 'tls' and start the TLS handshake upcall with the default PSK. When TLS is started the PSK key serial number is displayed in the sysfs attribute 'tls_key'
--- drivers/nvme/host/Kconfig | 15 ++++ drivers/nvme/host/core.c | 2 +- drivers/nvme/host/fabrics.c | 12 ++++ drivers/nvme/host/fabrics.h | 3 + drivers/nvme/host/nvme.h | 1 + drivers/nvme/host/sysfs.c | 21 ++++++ drivers/nvme/host/tcp.c | 140 ++++++++++++++++++++++++++++++++++-- 7 files changed, 187 insertions(+), 7 deletions(-)
drivers/nvme/host/Kconfig +15 -0
@@ -92,6 +92,21 @@ config NVME_TCP If unsure, say N. +config NVME_TCP_TLS + bool "NVMe over Fabrics TCP TLS encryption support" + depends on NVME_TCP + select NVME_COMMON + select NVME_KEYRING + select NET_HANDSHAKE + select KEYS + help + Enables TLS encryption for NVMe TCP using the netlink handshake API. + + The TLS handshake daemon is availble at + https://github.com/oracle/ktls-utils. + + If unsure, say N. + config NVME_AUTH bool "NVM Express over Fabrics In-Band Authentication" depends on NVME_CORE
drivers/nvme/host/core.c +1 -1
@@ -4380,7 +4380,7 @@ static void nvme_free_ctrl(struct device *dev)if (!subsys || ctrl->instance != subsys->instance)ida_free (&nvme_instance_ida, ctrl->instance); - +key_put (ctrl->tls_key);nvme_free_cels (ctrl);nvme_mpath_uninit (ctrl);nvme_auth_stop (ctrl);
drivers/nvme/host/fabrics.c +12 -0
@@ -647,6 +647,9 @@ static const match_table_t opt_tokens = { { NVMF_OPT_DISCOVERY, "discovery" }, { NVMF_OPT_DHCHAP_SECRET, "dhchap_secret=%s" }, { NVMF_OPT_DHCHAP_CTRL_SECRET, "dhchap_ctrl_secret=%s" }, +#ifdef CONFIG_NVME_TCP_TLS + { NVMF_OPT_TLS, "tls" }, +#endif { NVMF_OPT_ERR, NULL } };
@@ -671,6 +674,7 @@ static int nvmf_parse_options(struct nvmf_ctrl_options *opts, opts->hdr_digest = false; opts->data_digest = false; opts->tos =-1 ;/* < 0 == use transport default */ + opts->tls = false; options = o =kstrdup (buf,GFP_KERNEL );if (!options)
@@ -955,6 +959,14 @@ static int nvmf_parse_options(struct nvmf_ctrl_options *opts,kfree (opts->dhchap_ctrl_secret); opts->dhchap_ctrl_secret = p;break ; +case NVMF_OPT_TLS : +if (!IS_ENABLED (CONFIG_NVME_TCP_TLS )) { +pr_err ("TLS is not supported\n" ); + ret = -EINVAL ; + goto out; + } + opts->tls = true; +break ;default :pr_warn ("unknown parameter or missing value '%s' in ctrl creation request\n" , p);
drivers/nvme/host/fabrics.h +3 -0
@@ -70,6 +70,7 @@ enum {NVMF_OPT_DISCOVERY =1 <<22 ,NVMF_OPT_DHCHAP_SECRET =1 <<23 ,NVMF_OPT_DHCHAP_CTRL_SECRET =1 <<24 , + NVMF_OPT_TLS = 1 << 25, };/**
@@ -102,6 +103,7 @@ enum {* @dhchap_secret: DH-HMAC-CHAP secret * @dhchap_ctrl_secret: DH-HMAC-CHAP controller secret for bi-directional * authentication +* @tls: Start TLS encrypted connections (TCP) * @disable_sqflow: disable controller sq flow control * @hdr_digest: generate/verify header digest (TCP) * @data_digest: generate/verify data digest (TCP)
@@ -128,6 +130,7 @@ struct nvmf_ctrl_options {struct nvmf_host *host;char *dhchap_secret;char *dhchap_ctrl_secret; +bool tls;bool disable_sqflow;bool hdr_digest;bool data_digest;
drivers/nvme/host/nvme.h +1 -0
@@ -357,6 +357,7 @@ struct nvme_ctrl {struct nvme_dhchap_key *ctrl_key;u16 transaction;#endif +struct key *tls_key;/* Power saving configuration */ u64 ps_max_latency_us;
drivers/nvme/host/sysfs.c +21 -0
@@ -527,6 +527,19 @@ static DEVICE_ATTR(dhchap_ctrl_secret, S_IRUGO | S_IWUSR, nvme_ctrl_dhchap_ctrl_secret_show, nvme_ctrl_dhchap_ctrl_secret_store);#endif +#ifdef CONFIG_NVME_TCP_TLS +static ssize_t tls_key_show (struct device *dev, +struct device_attribute *attr,char *buf) +{ +struct nvme_ctrl *ctrl =dev_get_drvdata (dev); + +if (!ctrl->tls_key) +return 0 ; +return sysfs_emit (buf,"%08x" ,key_serial (ctrl->tls_key)); +} +static DEVICE_ATTR_RO (tls_key); +#endif +static struct attribute *nvme_dev_attrs[] = { &dev_attr_reset_controller.attr, &dev_attr_rescan_controller.attr,
@@ -553,6 +566,9 @@ static struct attribute *nvme_dev_attrs[] = {#ifdef CONFIG_NVME_AUTH &dev_attr_dhchap_secret.attr, &dev_attr_dhchap_ctrl_secret.attr, +#endif +#ifdef CONFIG_NVME_TCP_TLS + &dev_attr_tls_key.attr, #endifNULL };
@@ -583,6 +599,11 @@ static umode_t nvme_dev_attrs_are_visible(struct kobject *kobj,if (a == &dev_attr_dhchap_ctrl_secret.attr && !ctrl->opts)return 0 ;#endif +#ifdef CONFIG_NVME_TCP_TLS +if (a == &dev_attr_tls_key.attr && + (!ctrl->opts ||strcmp (ctrl->opts->transport,"tcp" ))) +return 0 ; +#endif return a->mode; }
drivers/nvme/host/tcp.c +134 -6
195 lines not on this page · raw message
Signature · 1 line
2.35.3
Sagi Grimberg
maintainerRe: [PATCH 08/16] nvme-tcp: enable TLS handshake upcall
drivers/nvme/host/tcp.c static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl) · line 1930
Quoted 11 lines
drivers/nvme/host/tcp.c +5
-0@@ -1802,9 +1922,17 @@ static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl)static int __nvme_tcp_alloc_io_queues (struct nvme_ctrl *ctrl) {int i, ret; +key_serial_t pskid =0 ; +if (ctrl->opts->tls) { +if (!ctrl->tls_key) { +dev_err (ctrl->device,"no PSK negotiated\n" ); +return -ENOKEY ;
This is really unexpected. its not that no PSK negotiated, something went awfully wrong if the psk wasn't negotiated and we still end up being here... Or there is a flow that can make this happen?
drivers/nvme/host/tcp.c static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl) · line 1933
Quoted 3 lines
drivers/nvme/host/tcp.c +3
-0+ } + pskid =key_serial (ctrl->tls_key); + }
newline missing.
key_serial can operate on null.
drivers/nvme/host/tcp.c static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl) · line 1938
Quoted 6 lines
drivers/nvme/host/tcp.c +1
-1for (i =1 ; i < ctrl->queue_count; i++) { - ret =nvme_tcp_alloc_queue (ctrl, i); + ret =nvme_tcp_alloc_queue (ctrl, i, pskid);if (ret) goto out_free_queues; }
Perhaps do:
--
@@ -1793,7 +1793,7 @@ static int __nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl)
int i, ret;
for (i = 1; i < ctrl->queue_count; i++) {
- ret = nvme_tcp_alloc_queue(ctrl, i);
+ ret = nvme_tcp_alloc_queue(ctrl, i, key_serial(ctrl->tls_key));
if (ret)
goto out_free_queues;
}
@@ -1812,6 +1812,9 @@ static int nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl)
unsigned int nr_io_queues;
int ret;+ if (ctrl->opts->tls && !ctrl->tls_key)
+ return -ENOKEY;
+
nr_io_queues = nvmf_nr_io_queues(ctrl->opts);
ret = nvme_set_queue_count(ctrl, &nr_io_queues);
if (ret)--
Quoted 9 lines
drivers/nvme/host/tcp.c +1
-1@@ -2631,7 +2759,7 @@ static struct nvmf_transport_ops nvme_tcp_transport = {NVMF_OPT_HOST_TRADDR |NVMF_OPT_CTRL_LOSS_TMO |NVMF_OPT_HDR_DIGEST |NVMF_OPT_DATA_DIGEST |NVMF_OPT_NR_WRITE_QUEUES |NVMF_OPT_NR_POLL_QUEUES | - NVMF_OPT_TOS | NVMF_OPT_HOST_IFACE, + NVMF_OPT_TOS | NVMF_OPT_HOST_IFACE | NVMF_OPT_TLS, .create_ctrl = nvme_tcp_create_ctrl, };
Re: [PATCH 08/16] nvme-tcp: enable TLS handshake upcall
Quoted 16 lines · Sagi Grimberg
drivers/nvme/host/tcp.c static int nvme_tcp_alloc_admin_queue(struct · line 1930
Quoted 11 lines
drivers/nvme/host/tcp.c +5
-0@@ -1802,9 +1922,17 @@ static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl) static int __nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl) { int i, ret; + key_serial_t pskid = 0; + if (ctrl->opts->tls) { + if (!ctrl->tls_key) { + dev_err(ctrl->device, "no PSK negotiated\n"); + return -ENOKEY;This is really unexpected. its not that no PSK negotiated, something went awfully wrong if the psk wasn't negotiated and we still end up being here... Or there is a flow that can make this happen?
Yeah, it _is_ unexpected.
But we're having two conditions here (->tls and ->tls_key), and we need to check for both to be true. Although, truth to be said, we might get away with just checking for ->tls_key; I'll check.
Quoted 38 lines
drivers/nvme/host/tcp.c static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl) · line 1933
Quoted 3 lines
drivers/nvme/host/tcp.c +3
-0+ } + pskid = key_serial(ctrl->tls_key); + }newline missing.
key_serialcan operate on null.drivers/nvme/host/tcp.c static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl) · line 1938
Quoted 6 lines
drivers/nvme/host/tcp.c +1
-1for (i = 1; i < ctrl->queue_count; i++) { - ret = nvme_tcp_alloc_queue(ctrl, i); + ret = nvme_tcp_alloc_queue(ctrl, i, pskid); if (ret) goto out_free_queues; }Perhaps do:
drivers/nvme/host/tcp.c +1
-1@@ -1793,7 +1793,7 @@ static int __nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl) int i, ret; for (i = 1; i < ctrl->queue_count; i++) { - ret = nvme_tcp_alloc_queue(ctrl, i); + ret = nvme_tcp_alloc_queue(ctrl, i,key_serial (ctrl->tls_key)); if (ret)goto
out_free_queues;
}(quoted diff) +3
-0@@ -1812,6 +1812,9 @@ static int nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl) unsigned int nr_io_queues; int ret; + if (ctrl->opts->tls && !ctrl->tls_key) + return -ENOKEY; + nr_io_queues = nvmf_nr_io_queues(ctrl->opts); ret = nvme_set_queue_count(ctrl, &nr_io_queues);
Quoted 3 lines
if (ret)
Yeah, might be simpler. I'll give it a go.
Cheers,
Hannes
PATCH v6 9/16 nvme-tcp: control message handling for recvmsg()
In reply to Hannes ReineckekTLS is sending TLS ALERT messages as control messages for recvmsg(). As we can't do anything sensible with it just abort the connection and let the userspace agent to a re-negotiation.
--- drivers/nvme/host/tcp.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-)
drivers/nvme/host/tcp.c +16 -1
@@ -14,6 +14,7 @@#include <net/sock.h> #include <net/tcp.h> #include <net/tls.h> +#include <net/tls_prot.h> #include <net/handshake.h> #include <linux/blk-mq.h> #include <crypto/hash.h>
@@ -1369,6 +1370,8 @@ static int nvme_tcp_init_connection(struct nvme_tcp_queue *queue) {struct nvme_tcp_icreq_pdu *icreq;struct nvme_tcp_icresp_pdu *icresp; +char cbuf[CMSG_LEN (sizeof (char ))] = {}; +u8 ctype;struct msghdr msg = {};struct kvec iov;bool ctrl_hdgst, ctrl_ddgst;
@@ -1406,11 +1409,23 @@ static int nvme_tcp_init_connection(struct nvme_tcp_queue *queue)memset (&msg,0 ,sizeof (msg)); iov.iov_base = icresp; iov.iov_len =sizeof (*icresp); +if (queue->ctrl->ctrl.opts->tls) { + msg.msg_control = cbuf; + msg.msg_controllen =sizeof (cbuf); + } ret =kernel_recvmsg (queue->sock, &msg, &iov,1 , iov.iov_len, msg.msg_flags);if (ret <0 ) goto free_icresp; - +if (queue->ctrl->ctrl.opts->tls) { + ctype =tls_get_record_type (queue->sock->sk, + (struct cmsghdr *)cbuf); +if (ctype !=TLS_RECORD_TYPE_DATA ) { +pr_err ("queue %d: unhandled TLS record %d\n" , +nvme_tcp_queue_id (queue), ctype); +return -ENOTCONN ; + } + } ret = -EINVAL ;if (icresp->hdr.type != nvme_tcp_icresp) { pr_err("queue %d: bad type returned %d\n",
Signature · 1 line
2.35.3
PATCH v6 10/16 nvme-fabrics: parse options 'keyring' and 'tls_key'
In reply to Hannes ReineckeParse the fabrics options 'keyring' and 'tls_key' and store the referenced keys in the options structure.
--- drivers/nvme/host/fabrics.c | 71 ++++++++++++++++++++++++++++++++++++- drivers/nvme/host/fabrics.h | 6 ++++ drivers/nvme/host/tcp.c | 11 ++++-- 3 files changed, 84 insertions(+), 4 deletions(-)
drivers/nvme/host/fabrics.c +70 -1
@@ -622,6 +622,41 @@ static struct nvmf_transport_ops *nvmf_lookup_transport(return NULL ; } +static int parse_key (struct nvmf_ctrl_options *opts,int key_id, +bool is_key) +{ +struct key *key =NULL ; + +if (key_id <0 ) { +pr_err ("Invalid %s id %d\n" , + is_key ?"key" :"keyring" , key_id); +return -EINVAL ; + } +if (key_id) { + key =key_lookup (key_id); +if (!key) { +pr_err ("%s id %08x not found\n" , + is_key ?"Key" :"Keyring" , key_id); +return -ENOKEY ; + } + }else { +if (is_key) +pr_debug ("Using 'best' PSK\n" ); +else +pr_debug ("Using default keyring\n" ); + key =NULL ; + } +if (is_key) { +key_put (opts->tls_key); + opts->tls_key = key; + }else { +key_put (opts->keyring); + opts->keyring = key; + } + +return 0 ; +} +static const match_table_t opt_tokens = { {NVMF_OPT_TRANSPORT ,"transport=%s" }, {NVMF_OPT_TRADDR ,"traddr=%s" },
@@ -643,6 +678,10 @@ static const match_table_t opt_tokens = { { NVMF_OPT_NR_WRITE_QUEUES, "nr_write_queues=%d" }, { NVMF_OPT_NR_POLL_QUEUES, "nr_poll_queues=%d" }, { NVMF_OPT_TOS, "tos=%d" }, +#ifdef CONFIG_NVME_TCP_TLS + { NVMF_OPT_KEYRING, "keyring=%d" }, + { NVMF_OPT_TLS_KEY, "tls_key=%d" }, +#endif { NVMF_OPT_FAIL_FAST_TMO, "fast_io_fail_tmo=%d" }, { NVMF_OPT_DISCOVERY, "discovery" }, { NVMF_OPT_DHCHAP_SECRET, "dhchap_secret=%s" },
@@ -660,7 +699,7 @@ static int nvmf_parse_options(struct nvmf_ctrl_options *opts,char *options, *o, *p;int token, ret =0 ;size_t nqnlen =0 ; -int ctrl_loss_tmo =NVMF_DEF_CTRL_LOSS_TMO ; +int ctrl_loss_tmo =NVMF_DEF_CTRL_LOSS_TMO , key_id;uuid_t hostid;char hostnqn[NVMF_NQN_SIZE ];
@@ -928,6 +967,34 @@ static int nvmf_parse_options(struct nvmf_ctrl_options *opts, } opts->tos = token;break ; +case NVMF_OPT_KEYRING : +if (!IS_ENABLED (CONFIG_NVME_TCP_TLS )) { +pr_err ("TLS is not supported\n" ); + ret = -EINVAL ; + goto out; + } +if (match_int (args, &key_id)) { + ret = -EINVAL ; + goto out; + } + ret =parse_key (opts, key_id, false); +if (ret <0 ) + goto out; +break ; +case NVMF_OPT_TLS_KEY : +if (!IS_ENABLED (CONFIG_NVME_TCP_TLS )) { +pr_err ("TLS is not supported\n" ); + ret = -EINVAL ; + goto out; + } +if (match_int (args, &key_id)) { + ret = -EINVAL ; + goto out; + } + ret =parse_key (opts, key_id, true); +if (ret <0 ) + goto out; +break ;case NVMF_OPT_DISCOVERY : opts->discovery_nqn = true;break ;
@@ -1168,6 +1235,8 @@ static int nvmf_check_allowed_opts(struct nvmf_ctrl_options *opts,void nvmf_free_options (struct nvmf_ctrl_options *opts) {nvmf_host_put (opts->host); +key_put (opts->keyring); +key_put (opts->tls_key);kfree (opts->transport);kfree (opts->traddr);kfree (opts->trsvcid);
drivers/nvme/host/fabrics.h +6 -0
@@ -71,6 +71,8 @@ enum {NVMF_OPT_DHCHAP_SECRET =1 <<23 ,NVMF_OPT_DHCHAP_CTRL_SECRET =1 <<24 ,NVMF_OPT_TLS =1 <<25 , +NVMF_OPT_KEYRING =1 <<26 , + NVMF_OPT_TLS_KEY = 1 << 27, };/**
@@ -103,6 +105,8 @@ enum {* @dhchap_secret: DH-HMAC-CHAP secret * @dhchap_ctrl_secret: DH-HMAC-CHAP controller secret for bi-directional * authentication +* @keyring: Keyring to use for key lookups +* @tls_key: TLS key for encrypted connections (TCP) * @tls: Start TLS encrypted connections (TCP) * @disable_sqflow: disable controller sq flow control * @hdr_digest: generate/verify header digest (TCP)
@@ -130,6 +134,8 @@ struct nvmf_ctrl_options {struct nvmf_host *host;char *dhchap_secret;char *dhchap_ctrl_secret; +struct key *keyring; +struct key *tls_key;bool tls;bool disable_sqflow;bool hdr_digest;
drivers/nvme/host/tcp.c +8 -3
@@ -1583,6 +1583,8 @@ static int nvme_tcp_start_tls(struct nvme_ctrl *nctrl,dev_dbg (nctrl->device,"queue %d: start TLS with key %x\n" , qid, pskid); +if (nctrl->opts->keyring) + keyring =key_serial (nctrl->opts->keyring);memset (&args,0 ,sizeof (args)); args.ta_sock = queue->sock; args.ta_done = nvme_tcp_tls_done;
@@ -1909,9 +1911,12 @@ static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl)key_serial_t pskid =0 ;if (ctrl->opts->tls) { - pskid =nvme_tls_psk_default (NULL , - ctrl->opts->host->nqn, - ctrl->opts->subsysnqn); +if (ctrl->opts->tls_key) + pskid =key_serial (ctrl->opts->tls_key); +else + pskid =nvme_tls_psk_default (ctrl->opts->keyring, + ctrl->opts->host->nqn, + ctrl->opts->subsysnqn);if (!pskid) {dev_err (ctrl->device,"no valid PSK found\n" ); ret = -ENOKEY ;
Signature · 1 line
2.35.3
Sagi Grimberg
maintainerRe: [PATCH 10/16] nvme-fabrics: parse options 'keyring' and 'tls_key'
Quoted 31 lines · Hannes Reinecke
Parse the fabrics options 'keyring' and '
tls_key' and store the referenced keys in the options structure.Signed-off-by Hannes Reinecke <[email protected]>--- drivers/nvme/host/fabrics.c | 71 ++++++++++++++++++++++++++++++++++++- drivers/nvme/host/fabrics.h | 6 ++++ drivers/nvme/host/tcp.c | 11 ++++-- 3 files changed, 84 insertions(+), 4 deletions(-)drivers/nvme/host/fabrics.c +13
-0@@ -622,6 +622,41 @@ static struct nvmf_transport_ops *nvmf_lookup_transport(return NULL ; } +static int parse_key (struct nvmf_ctrl_options *opts,int key_id, +bool is_key) +{ +struct key *key =NULL ; + +if (key_id <0 ) { +pr_err ("Invalid %s id %d\n" , + is_key ?"key" :"keyring" , key_id); +return -EINVAL ; + } +if (key_id) { + key =key_lookup (key_id); +if (!key) {
drivers/nvme/host/fabrics.c static struct nvmf_transport_ops *nvmf_lookup_transport( · line 647
Quoted 10 lines
drivers/nvme/host/fabrics.c +10
-0+pr_err ("%s id %08x not found\n" , + is_key ?"Key" :"Keyring" , key_id); +return -ENOKEY ; + } + }else { +if (is_key) +pr_debug ("Using 'best' PSK\n" ); +else +pr_debug ("Using default keyring\n" ); + key =NULL ;
Not sure I understand the else case here. Why do we allow key_id = 0 if it does not represent a valid existing key_id?
drivers/nvme/host/fabrics.c static struct nvmf_transport_ops *nvmf_lookup_transport( · line 656
Quoted 9 lines
drivers/nvme/host/fabrics.c +9
-0+ } +if (is_key) { +key_put (opts->tls_key); + opts->tls_key = key; + }else { +key_put (opts->keyring); + opts->keyring = key; + } +
Perhaps instead of is_key, just return the key and assign outside.
Re: [PATCH 10/16] nvme-fabrics: parse options 'keyring' and 'tls_key'
Quoted 40 lines · Sagi Grimberg
Quoted 37 lines · Hannes Reinecke
Parse the fabrics options 'keyring' and '
tls_key' and store the referenced keys in the options structure.Signed-off-by Hannes Reinecke <[email protected]>---
drivers/nvme/host/fabrics.c| 71 ++++++++++++++++++++++++++++++++++++-drivers/nvme/host/fabrics.h| 6 ++++ drivers/nvme/host/tcp.c | 11 ++++--3 files changed, 84 insertions(+), 4 deletions(-)drivers/nvme/host/fabrics.c +19
-0@@ -622,6 +622,41 @@ static struct nvmf_transport_ops *nvmf_lookup_transport( return NULL; } +static int parse_key (struct nvmf_ctrl_options *opts,int key_id, + bool is_key) +{ + struct key *key = NULL; + + if (key_id < 0) { + pr_err("Invalid %s id %d\n", + is_key ? "key" : "keyring", key_id); + return -EINVAL; + } + if (key_id) { + key = key_lookup(key_id); + if (!key) { + pr_err("%s id %08x not found\n", + is_key ? "Key" : "Keyring", key_id); + return -ENOKEY; + } + } else { + if (is_key)
Quoted 9 lines
drivers/nvme/host/fabrics.c static struct nvmf_transport_ops *nvmf_lookup_transport( · line 647
Quoted 4 lines
drivers/nvme/host/fabrics.c +4
-0+ pr_debug("Using 'best' PSK\n"); + else + pr_debug("Using default keyring\n"); + key = NULL;Not sure I understand the else case here. Why do we allow
key_id= 0 if it does not represent a valid existingkey_id?
No, you are right. While there is a default keyring, there is no point in allowing '0' as a value here; if the user wants to use the default keyring he shoudn't have set the '--keyring' option.
Quoted 11 lines
drivers/nvme/host/fabrics.c static struct nvmf_transport_ops *nvmf_lookup_transport( · line 656
Quoted 9 lines
drivers/nvme/host/fabrics.c +9
-0+ } + if (is_key) { + key_put(opts->tls_key); + opts->tls_key = key; + } else { + key_put(opts->keyring); + opts->keyring = key; + } +Perhaps instead of
is_key, just return the key and assign outside.
Could be. Lemme see.
Cheers,
Hannes
PATCH v6 11/16 nvmet: make TCP sectype settable via configfs
In reply to Hannes ReineckeAdd a new configfs attribute 'addr_tsas' to make the TCP sectype settable via configfs.
--- drivers/nvme/target/configfs.c | 65 ++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+)
drivers/nvme/target/configfs.c +65 -0
@@ -303,6 +303,11 @@ static void nvmet_port_init_tsas_rdma(struct nvmet_port *port) port->disc_addr.tsas.rdma.cms =NVMF_RDMA_CMS_RDMA_CM ; } +static void nvmet_port_init_tsas_tcp (struct nvmet_port *port,int sectype) +{ + port->disc_addr.tsas.tcp.sectype = sectype; +} +static ssize_t nvmet_addr_trtype_store (struct config_item *item,const char *page,size_t count) {
@@ -325,11 +330,70 @@ static ssize_t nvmet_addr_trtype_store(struct config_item *item, port->disc_addr.trtype = nvmet_transport[i].type;if (port->disc_addr.trtype ==NVMF_TRTYPE_RDMA )nvmet_port_init_tsas_rdma (port); +else if (port->disc_addr.trtype ==NVMF_TRTYPE_TCP ) +nvmet_port_init_tsas_tcp (port,NVMF_TCP_SECTYPE_NONE );return count; }CONFIGFS_ATTR (nvmet_, addr_trtype); +static const struct nvmet_type_name_map nvmet_addr_tsas_tcp[] = { + {NVMF_TCP_SECTYPE_NONE ,"none" }, + {NVMF_TCP_SECTYPE_TLS13 ,"tls1.3" }, +}; + +static const struct nvmet_type_name_map nvmet_addr_tsas_rdma[] = { + {NVMF_RDMA_QPTYPE_CONNECTED ,"connected" }, + {NVMF_RDMA_QPTYPE_DATAGRAM ,"datagram" }, +}; + +static ssize_t nvmet_addr_tsas_show (struct config_item *item, +char *page) +{ +struct nvmet_port *port =to_nvmet_port (item); +int i; + +if (port->disc_addr.trtype ==NVMF_TRTYPE_TCP ) { +for (i =0 ; i <ARRAY_SIZE (nvmet_addr_tsas_tcp); i++) { +if (port->disc_addr.tsas.tcp.sectype == nvmet_addr_tsas_tcp[i].type) +return sprintf (page,"%s\n" , nvmet_addr_tsas_tcp[i].name); + } + }else if (port->disc_addr.trtype ==NVMF_TRTYPE_RDMA ) { +for (i =0 ; i <ARRAY_SIZE (nvmet_addr_tsas_rdma); i++) { +if (port->disc_addr.tsas.rdma.qptype == nvmet_addr_tsas_rdma[i].type) +return sprintf (page,"%s\n" , nvmet_addr_tsas_rdma[i].name); + } + } +return sprintf (page,"reserved\n" ); +} + +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); +int i; + +if (nvmet_is_port_enabled (port, __func__)) +return -EACCES ; + +if (port->disc_addr.trtype !=NVMF_TRTYPE_TCP ) +return -EINVAL ; + +for (i =0 ; i <ARRAY_SIZE (nvmet_addr_tsas_tcp); i++) { +if (sysfs_streq (page, nvmet_addr_tsas_tcp[i].name)) + goto found; + } + +pr_err ("Invalid value '%s' for tsas\n" , page); +return -EINVAL ; + +found: +nvmet_port_init_tsas_tcp (port, nvmet_addr_tsas_tcp[i].type); +return count; +} + +CONFIGFS_ATTR (nvmet_, addr_tsas); +/* * Namespace structures & file operation functions below */
@@ -1741,6 +1805,7 @@ static struct configfs_attribute *nvmet_port_attrs[] = { &nvmet_attr_addr_traddr, &nvmet_attr_addr_trsvcid, &nvmet_attr_addr_trtype, + &nvmet_attr_addr_tsas, &nvmet_attr_param_inline_data_size, #ifdef CONFIG_BLK_DEV_INTEGRITY &nvmet_attr_param_pi_enable,
Signature · 1 line
2.35.3
PATCH v6 12/16 nvmet-tcp: make nvmet_tcp_alloc_queue() a void function
In reply to Hannes ReineckeThe return value from nvmet_tcp_alloc_queue() are just used to figure out if sock_release() need to be called. So this patch moves sock_release() into nvmet_tcp_alloc_queue() and make it a void function.
--- drivers/nvme/target/tcp.c | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-)
drivers/nvme/target/tcp.c +7 -9
@@ -1621,7 +1621,7 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue)return ret; } -static int nvmet_tcp_alloc_queue (struct nvmet_tcp_port *port, +static void nvmet_tcp_alloc_queue (struct nvmet_tcp_port *port,struct socket *newsock) {struct nvmet_tcp_queue *queue;
@@ -1629,7 +1629,7 @@ static int nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port, queue =kzalloc (sizeof (*queue),GFP_KERNEL );if (!queue) -return -ENOMEM ; + goto out_release;INIT_WORK (&queue->release_work, nvmet_tcp_release_queue_work);INIT_WORK (&queue->io_work, nvmet_tcp_io_work);
@@ -1666,7 +1666,7 @@ static int nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,if (ret) goto out_destroy_sq; -return 0 ; +return ; out_destroy_sq:mutex_lock (&nvmet_tcp_queue_mutex);list_del_init (&queue->queue_list);
@@ -1678,7 +1678,9 @@ static int nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,ida_free (&nvmet_tcp_queue_ida, queue->idx); out_free_queue:kfree (queue); -return ret; +out_release: +pr_err ("failed to allocate queue\n" ); +sock_release (newsock); }static void nvmet_tcp_accept_work (struct work_struct *w)
@@ -1695,11 +1697,7 @@ static void nvmet_tcp_accept_work(struct work_struct *w)pr_warn ("failed to accept err=%d\n" , ret);return ; } - ret =nvmet_tcp_alloc_queue (port, newsock); -if (ret) { -pr_err ("failed to allocate queue\n" ); -sock_release (newsock); - } +nvmet_tcp_alloc_queue (port, newsock); } }
Signature · 1 line
2.35.3
Re: [PATCH 12/16] nvmet-tcp: make nvmet_tcp_alloc_queue() a void function
OK,
PATCH v6 13/16 nvmet-tcp: allocate socket file
In reply to Hannes ReineckeFor the TLS upcall we need to allocate a socket file such that the userspace daemon is able to use the socket.
--- drivers/nvme/target/tcp.c | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-)
drivers/nvme/target/tcp.c +14 -4
@@ -1493,12 +1493,12 @@ static void nvmet_tcp_release_queue_work(struct work_struct *w)nvmet_sq_destroy (&queue->nvme_sq);cancel_work_sync (&queue->io_work);nvmet_tcp_free_cmd_data_in_buffers (queue); -sock_release (queue->sock); +/* ->sock will be released by fput() */ +fput (queue->sock->file);nvmet_tcp_free_cmds (queue);if (queue->hdr_digest || queue->data_digest)nvmet_tcp_free_crypto (queue);ida_free (&nvmet_tcp_queue_ida, queue->idx); - page =virt_to_head_page (queue->pf_cache.va);__page_frag_cache_drain (page, queue->pf_cache.pagecnt_bias);kfree (queue);
@@ -1625,6 +1625,7 @@ static void nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port, struct socket *newsock) {struct nvmet_tcp_queue *queue; +struct file *sock_file =NULL ;int ret; queue =kzalloc (sizeof (*queue),GFP_KERNEL );
@@ -1642,10 +1643,16 @@ static void nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,init_llist_head (&queue->resp_list);INIT_LIST_HEAD (&queue->resp_send_list); + sock_file =sock_alloc_file (queue->sock,O_CLOEXEC ,NULL ); +if (IS_ERR (sock_file)) { + ret =PTR_ERR (sock_file); + goto out_free_queue; + } + queue->idx =ida_alloc (&nvmet_tcp_queue_ida,GFP_KERNEL );if (queue->idx <0 ) { ret = queue->idx; - goto out_free_queue; + goto out_sock; } ret =nvmet_tcp_alloc_cmd (queue, &queue->connect);
@@ -1676,11 +1683,14 @@ static void nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,nvmet_tcp_free_cmd (&queue->connect); out_ida_remove:ida_free (&nvmet_tcp_queue_ida, queue->idx); +out_sock: +fput (queue->sock->file); out_free_queue:kfree (queue); out_release:pr_err ("failed to allocate queue\n" ); -sock_release (newsock); +if (!sock_file) +sock_release (newsock); }static void nvmet_tcp_accept_work (struct work_struct *w)
Signature · 1 line
2.35.3
Re: [PATCH 13/16] nvmet-tcp: allocate socket file
PATCH v6 14/16 nvmet: Allow to change 'TSAS' and 'TREQ'
In reply to Hannes ReineckeAllow to change 'TSAS' and 'TREQ' to values specified in the spec.
--- drivers/nvme/target/configfs.c | 36 +++++++++++++++++++++++++++++++--- 1 file changed, 33 insertions(+), 3 deletions(-)
drivers/nvme/target/configfs.c +33 -3
@@ -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; }
Signature · 1 line
2.35.3
Sagi Grimberg
maintainerRe: [PATCH 14/16] nvmet: Allow to change 'TSAS' and 'TREQ'
Quoted 1 line · Hannes Reinecke
Allow to change 'TSAS' and 'TREQ' to values specified in the spec.
I think a little more description is needed here. About the rules of how the two interact.
Quoted 11 lines
Signed-off-by Hannes Reinecke <[email protected]>--- drivers/nvme/target/configfs.c | 36 +++++++++++++++++++++++++++++++--- 1 file changed, 33 insertions(+), 3 deletions(-)drivers/nvme/target/configfs.c +0
-0
drivers/nvme/target/configfs.c static const struct nvmet_type_name_map nvmet_addr_treq[] = { · line 165
Quoted 7 lines
drivers/nvme/target/configfs.c +4
-0@@ -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 ); +}
The function name does not match what it does.
Quoted 11 lines
drivers/nvme/target/configfs.c +3
-2+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++) {
drivers/nvme/target/configfs.c static ssize_t nvmet_addr_treq_show(struct config_item *item, char *page) · line 185
Quoted 7 lines
drivers/nvme/target/configfs.c +4
-0@@ -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 ); +}
Same here, function name and what it returns seem diverged from each other.
Quoted 11 lines
drivers/nvme/target/configfs.c +2
-1+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__))
drivers/nvme/target/configfs.c static ssize_t nvmet_addr_treq_store(struct config_item *item, · line 209
Quoted 7 lines
drivers/nvme/target/configfs.c +4
-0@@ -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 ;
So what are you supposed to set in treq without tls?
Quoted 20 lines
drivers/nvme/target/configfs.c +6
-0+ }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);
drivers/nvme/target/configfs.c static ssize_t nvmet_addr_tsas_store(struct config_item *item, · line 421
Quoted 10 lines
drivers/nvme/target/configfs.c +10
-0+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;
Hmm, so setting tsas modifies treq under the hood. Surprising...
It is not clear to me what is the user supposed to set in configfs. Just set tsas to tls1.3 and that's it? any treq setting will not be allowed after it? Its a bit confusing.
Re: [PATCH 14/16] nvmet: Allow to change 'TSAS' and 'TREQ'
Quoted 8 lines · Sagi Grimberg
Quoted 1 line · Hannes Reinecke
Allow to change 'TSAS' and 'TREQ' to values specified in the spec.
I think a little more description is needed here. About the rules of how the two interact.
Ok.
Quoted 6 lines
Quoted 6 lines
Signed-off-by Hannes Reinecke <[email protected]>---
drivers/nvme/target/configfs.c| 36 +++++++++++++++++++++++++++++++---1 file changed, 33 insertions(+), 3 deletions(-)
Quoted 15 lines
drivers/nvme/target/configfs.c static const struct nvmet_type_name_map · line 165
Quoted 12 lines
drivers/nvme/target/configfs.c +4
-0@@ -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); +}The function name does not match what it does.
nvmet_port_addr_treq() ?
Quoted 12 lines
Quoted 12 lines
drivers/nvme/target/configfs.c +3
-2+ 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");
Quoted 9 lines
drivers/nvme/target/configfs.c static ssize_t nvmet_addr_treq_show(struct config_item *item, char *page) · line 185
Quoted 5 lines
drivers/nvme/target/configfs.c +4
-0} +static inline u8 nvmet_port_treq_mask (struct nvmet_port *port) +{ + return (port->disc_addr.treq & ~NVME_TREQ_SECURE_CHANNEL_MASK); +}Same here, function name and what it returns seem diverged from each other.
nvmet_port_addr_treq_mask() ?
Quoted 12 lines
Quoted 12 lines
drivers/nvme/target/configfs.c +2
-1+ 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(structconfig_item *item, return -EINVAL;
Quoted 9 lines
Quoted 6 lines
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;So what are you supposed to set in treq without tls?
'not specified' is the only valid choice currrently.
Quoted 35 lines
Quoted 23 lines
+ } 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;drivers/nvme/target/configfs.c +1
-0@@ -371,6 +390,7 @@ static ssize_t nvmet_addr_tsas_store(structconfig_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)Quoted 8 lines
+ 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;Hmm, so setting tsas modifies treq under the hood. Surprising...
Quoted 3 lines
It is not clear to me what is the user supposed to set in configfs. Just set tsas to tls1.3 and that's it? any treq setting will not be allowed after it? Its a bit confusing.
Yeah, it is. I guess we should disallow setting of the 'treq' bit from the user, as it's pretty much defined by the TSAS value.
Will be modifying it.
Cheers,
Hannes
PATCH v6 15/16 nvmet-tcp: enable TLS handshake upcall
In reply to Hannes ReineckeAdd functions to start the TLS handshake upcall when the TCP TSAS sectype is set to 'tls1.3' and add a config option NVME_TARGET_TCP_TLS.
And move the 'state' lock to an irq-safe lock as the 'done' callback from the TLS handshake will be running in interrupt context.
--- drivers/nvme/target/Kconfig | 15 ++++ drivers/nvme/target/configfs.c | 27 ++++++++ drivers/nvme/target/nvmet.h | 1 + drivers/nvme/target/tcp.c | 123 +++++++++++++++++++++++++++++++-- 4 files changed, 161 insertions(+), 5 deletions(-)
drivers/nvme/target/Kconfig +15 -0
@@ -84,6 +84,21 @@ config NVME_TARGET_TCP If unsure, say N. +config NVME_TARGET_TCP_TLS + bool "NVMe over Fabrics TCP target TLS encryption support" + depends on NVME_TARGET_TCP + select NVME_COMMON + select NVME_KEYRING + select NET_HANDSHAKE + select KEYS + help + Enables TLS encryption for the NVMe TCP target using the netlink handshake API. + + The TLS handshake daemon is availble at + https://github.com/oracle/ktls-utils. + + If unsure, say N. + config NVME_TARGET_AUTH bool "NVMe over Fabrics In-band Authentication support" depends on NVME_TARGET
drivers/nvme/target/configfs.c +27 -0
@@ -15,6 +15,7 @@#ifdef CONFIG_NVME_TARGET_AUTH #include <linux/nvme-auth.h> #endif +#include <linux/nvme-keyring.h> #include <crypto/hash.h> #include <crypto/kpp.h>
@@ -204,6 +205,14 @@ static ssize_t nvmet_addr_treq_store(struct config_item *item, found:if (port->disc_addr.trtype ==NVMF_TRTYPE_TCP ) { +if (!IS_ENABLED (CONFIG_NVME_TARGET_TCP_TLS )) { +pr_err ("TLS is not supported\n" ); +return -EINVAL ; + } +if (!port->keyring) { +pr_err ("TLS keyring not configured\n" ); +return -EINVAL ; + }if (port->disc_addr.tsas.tcp.sectype !=NVMF_TCP_SECTYPE_TLS13 ) {pr_warn ("cannot change TREQ when TLS is not enabled\n" );return -EINVAL ;
@@ -399,6 +408,15 @@ static ssize_t nvmet_addr_tsas_store(struct config_item *item,if (port->disc_addr.trtype !=NVMF_TRTYPE_TCP )return -EINVAL ; +if (!IS_ENABLED (CONFIG_NVME_TARGET_TCP_TLS )) { +pr_err ("TLS is not supported\n" ); +return -EINVAL ; + } +if (!port->keyring) { +pr_err ("TLS keyring not configured\n" ); +return -EINVAL ; + } +for (i =0 ; i <ARRAY_SIZE (nvmet_addr_tsas_tcp); i++) {if (sysfs_streq (page, nvmet_addr_tsas_tcp[i].name)) goto found;
@@ -1825,6 +1843,7 @@ static void nvmet_port_release(struct config_item *item)flush_workqueue (nvmet_wq);list_del (&port->global_entry); +key_put (port->keyring);kfree (port->ana_state);kfree (port); }
@@ -1874,6 +1893,14 @@ static struct config_group *nvmet_ports_make(struct config_group *group,return ERR_PTR (-ENOMEM ); } +if (nvme_keyring_id ()) { + port->keyring =key_lookup (nvme_keyring_id ()); +if (IS_ERR (port->keyring)) { +pr_warn ("NVMe keyring not available, disabling TLS\n" ); + port->keyring =NULL ; + } + } +for (i =1 ; i <=NVMET_MAX_ANAGRPS ; i++) {if (i ==NVMET_DEFAULT_ANA_GRPID ) port->ana_state[1 ] =NVME_ANA_OPTIMIZED ;
drivers/nvme/target/nvmet.h +1 -0
@@ -158,6 +158,7 @@ struct nvmet_port {struct config_group ana_groups_group;struct nvmet_ana_group ana_default_group;enum nvme_ana_state *ana_state; +struct key *keyring;void *priv;bool enabled;int inline_data_size;
drivers/nvme/target/tcp.c +118 -5
184 lines not on this page · raw message
Signature · 1 line
2.35.3
Sagi Grimberg
maintainerRe: [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall
Quoted 6 lines · Hannes Reinecke
Add functions to start the TLS handshake upcall when the TCP TSAS sectype is set to 'tls1.3' and add a config option
NVME_TARGET_TCP_TLS.
And move the 'state' lock to an irq-safe lock as the 'done' callback from the TLS handshake will be running in interrupt context.
Really.. that is surprising. Can you describe how exactly?
Quoted 133 lines
Signed-off-by Hannes Reincke <[email protected]>--- drivers/nvme/target/Kconfig | 15 ++++ drivers/nvme/target/configfs.c | 27 ++++++++ drivers/nvme/target/nvmet.h | 1 + drivers/nvme/target/tcp.c | 123 +++++++++++++++++++++++++++++++-- 4 files changed, 161 insertions(+), 5 deletions(-)drivers/nvme/target/Kconfig +15
-0@@ -84,6 +84,21 @@ config NVME_TARGET_TCP If unsure, say N. +config NVME_TARGET_TCP_TLS + bool "NVMe over Fabrics TCP target TLS encryption support" + depends on NVME_TARGET_TCP + select NVME_COMMON + select NVME_KEYRING + select NET_HANDSHAKE + select KEYS + help + Enables TLS encryption for the NVMe TCP target using the netlink handshake API. + + The TLS handshake daemon is availble at + https://github.com/oracle/ktls-utils. + + If unsure, say N. + config NVME_TARGET_AUTH bool "NVMe over Fabrics In-band Authentication support" depends on NVME_TARGETdrivers/nvme/target/configfs.c +27
-0@@ -15,6 +15,7 @@#ifdef CONFIG_NVME_TARGET_AUTH #include <linux/nvme-auth.h> #endif +#include <linux/nvme-keyring.h> #include <crypto/hash.h> #include <crypto/kpp.h> @@ -204,6 +205,14 @@ static ssize_t nvmet_addr_treq_store(struct config_item *item, found:if (port->disc_addr.trtype ==NVMF_TRTYPE_TCP ) { +if (!IS_ENABLED (CONFIG_NVME_TARGET_TCP_TLS )) { +pr_err ("TLS is not supported\n" ); +return -EINVAL ; + } +if (!port->keyring) { +pr_err ("TLS keyring not configured\n" ); +return -EINVAL ; + }if (port->disc_addr.tsas.tcp.sectype !=NVMF_TCP_SECTYPE_TLS13 ) {pr_warn ("cannot change TREQ when TLS is not enabled\n" );return -EINVAL ;@@ -399,6 +408,15 @@ static ssize_t nvmet_addr_tsas_store(struct config_item *item,if (port->disc_addr.trtype !=NVMF_TRTYPE_TCP )return -EINVAL ; +if (!IS_ENABLED (CONFIG_NVME_TARGET_TCP_TLS )) { +pr_err ("TLS is not supported\n" ); +return -EINVAL ; + } +if (!port->keyring) { +pr_err ("TLS keyring not configured\n" ); +return -EINVAL ; + } +for (i =0 ; i <ARRAY_SIZE (nvmet_addr_tsas_tcp); i++) {if (sysfs_streq (page, nvmet_addr_tsas_tcp[i].name)) goto found;@@ -1825,6 +1843,7 @@ static void nvmet_port_release(struct config_item *item)flush_workqueue (nvmet_wq);list_del (&port->global_entry); +key_put (port->keyring);kfree (port->ana_state);kfree (port); }@@ -1874,6 +1893,14 @@ static struct config_group *nvmet_ports_make(struct config_group *group,return ERR_PTR (-ENOMEM ); } +if (nvme_keyring_id ()) { + port->keyring =key_lookup (nvme_keyring_id ()); +if (IS_ERR (port->keyring)) { +pr_warn ("NVMe keyring not available, disabling TLS\n" ); + port->keyring =NULL ; + } + } +for (i =1 ; i <=NVMET_MAX_ANAGRPS ; i++) {if (i ==NVMET_DEFAULT_ANA_GRPID ) port->ana_state[1 ] =NVME_ANA_OPTIMIZED ;drivers/nvme/target/nvmet.h +1
-0@@ -158,6 +158,7 @@ struct nvmet_port {struct config_group ana_groups_group;struct nvmet_ana_group ana_default_group;enum nvme_ana_state *ana_state; +struct key *keyring;void *priv;bool enabled;int inline_data_size;drivers/nvme/target/tcp.c +4
-0@@ -8,9 +8,13 @@#include <linux/init.h> #include <linux/slab.h> #include <linux/err.h> +#include <linux/key.h> #include <linux/nvme-tcp.h> +#include <linux/nvme-keyring.h> #include <net/sock.h> #include <net/tcp.h> +#include <net/tls.h> +#include <net/handshake.h> #include <linux/inet.h> #include <linux/llist.h> #include <crypto/hash.h> @@ -66,6 +70,16 @@ device_param_cb(idle_poll_period_usecs, &set_param_ops, MODULE_PARM_DESC(idle_poll_period_usecs,
drivers/nvme/target/tcp.c device_param_cb(idle_poll_period_usecs, &set_param_ops, · line 80
Quoted 10 lines
drivers/nvme/target/tcp.c +8
-0"nvmet tcp io_work poll till idle time period in usecs: Default 0"); +#ifdef CONFIG_NVME_TARGET_TCP_TLS +/* +* TLS handshake timeout +*/ +static int tls_handshake_timeout =10 ; +module_param (tls_handshake_timeout, int,0644 ); +MODULE_PARM_DESC (tls_handshake_timeout, +"nvme TLS handshake timeout in seconds (default 30)" );
modparam description is lying...
Quoted 68 lines
drivers/nvme/target/tcp.c +25
-4+#endif +#define NVMET_TCP_RECV_BUDGET 8#define NVMET_TCP_SEND_BUDGET 8#define NVMET_TCP_IO_WORK_BUDGET 64@@ -122,6 +136,7 @@ struct nvmet_tcp_cmd {enum nvmet_tcp_queue_state {NVMET_TCP_Q_CONNECTING , +NVMET_TCP_Q_TLS_HANDSHAKE ,NVMET_TCP_Q_LIVE ,NVMET_TCP_Q_DISCONNECTING , };@@ -154,6 +169,8 @@ struct nvmet_tcp_queue {bool data_digest;struct ahash_request *snd_hash;struct ahash_request *rcv_hash; +key_serial_t tls_pskid; +struct delayed_work tls_handshake_work;unsigned long poll_end;@@ -1285,12 +1302,12 @@ static int nvmet_tcp_try_recv(struct nvmet_tcp_queue *queue,static void nvmet_tcp_schedule_release_queue (struct nvmet_tcp_queue *queue) { -spin_lock (&queue->state_lock); +spin_lock_irq (&queue->state_lock);if (queue->state !=NVMET_TCP_Q_DISCONNECTING ) { queue->state =NVMET_TCP_Q_DISCONNECTING ;queue_work (nvmet_wq, &queue->release_work); } -spin_unlock (&queue->state_lock); +spin_unlock_irq (&queue->state_lock); }static inline void nvmet_tcp_arm_queue_deadline (struct nvmet_tcp_queue *queue)@@ -1512,8 +1529,12 @@ static void nvmet_tcp_data_ready(struct sock *sk)read_lock_bh (&sk->sk_callback_lock); queue = sk->sk_user_data; -if (likely (queue)) -queue_work_on (queue_cpu (queue), nvmet_tcp_wq, &queue->io_work); +if (queue->data_ready) + queue->data_ready (sk); +if (likely (queue) && + queue->state !=NVMET_TCP_Q_TLS_HANDSHAKE ) +queue_work_on (queue_cpu (queue), nvmet_tcp_wq, + &queue->io_work);read_unlock_bh (&sk->sk_callback_lock); }@@ -1621,6 +1642,75 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue)return ret; } +#ifdef CONFIG_NVME_TARGET_TCP_TLS +static void nvmet_tcp_tls_handshake_done (void *data,int status, +key_serial_t peerid) +{ +struct nvmet_tcp_queue *queue = data; + +pr_debug ("queue %d: TLS handshake done, key %x, status %d\n" , + queue->idx, peerid, status); +spin_lock_irq (&queue->state_lock); +if (queue->state !=NVMET_TCP_Q_TLS_HANDSHAKE ) { +pr_warn ("queue %d: TLS handshake already completed\n" , + queue->idx);
drivers/nvme/target/tcp.c static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) · line 1666
Quoted 10 lines
drivers/nvme/target/tcp.c +10
-0+spin_unlock_irq (&queue->state_lock); +return ; + } +if (!status) + queue->tls_pskid = peerid; + queue->state =NVMET_TCP_Q_CONNECTING ; +spin_unlock_irq (&queue->state_lock); + +cancel_delayed_work_sync (&queue->tls_handshake_work); +if (status) {
I think that after this call, you cannot reference anything in queue as it may have been released. Or I'm missing something?
Quoted 18 lines
drivers/nvme/target/tcp.c +18
-0+nvmet_tcp_schedule_release_queue (queue); +return ; + } + +pr_debug ("queue %d: resetting queue callbacks after TLS handshake\n" , + queue->idx); +nvmet_tcp_set_queue_sock (queue); +} + +static void nvmet_tcp_tls_handshake_timeout_work (struct work_struct *w) +{ +struct nvmet_tcp_queue *queue =container_of (to_delayed_work (w), + struct nvmet_tcp_queue, tls_handshake_work); + +pr_debug ("queue %d: TLS handshake timeout\n" , queue->idx); +nvmet_tcp_tls_handshake_done ((void *)queue,ETIMEDOUT ,0 ); +} +
Re: [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall
Quoted 12 lines · Sagi Grimberg
Quoted 6 lines · Hannes Reinecke
Add functions to start the TLS handshake upcall when the TCP TSAS sectype is set to 'tls1.3' and add a config option
NVME_TARGET_TCP_TLS.
And move the 'state' lock to an irq-safe lock as the 'done' callback from the TLS handshake will be running in interrupt context.Really.. that is surprising. Can you describe how exactly?
Let me cross-check.
Quoted 135 lines
Quoted 135 lines
Signed-off-by Hannes Reincke <[email protected]>---
drivers/nvme/target/Kconfig | 15 ++++drivers/nvme/target/configfs.c| 27 ++++++++ drivers/nvme/target/nvmet.h | 1 + drivers/nvme/target/tcp.c | 123 +++++++++++++++++++++++++++++++--4 files changed, 161 insertions(+), 5 deletions(-)drivers/nvme/target/Kconfig +0
-0@@ -84,6 +84,21 @@ config NVME_TARGET_TCPIf unsure, say N.
+configNVME_TARGET_TCP_TLS
+ bool "NVMe over Fabrics TCP target TLS encryption support" + depends onNVME_TARGET_TCP
+ selectNVME_COMMON
+ selectNVME_KEYRING
+ selectNET_HANDSHAKE
+ select KEYS
+ help
+ Enables TLS encryption for the NVMe TCP target using the netlink handshake API.drivers/nvme/target/Kconfig +6
-0+ + The TLS handshake daemon is availble at + https://github.com/oracle/ktls-utils. + + If unsure, say N. +config
NVME_TARGET_AUTH
bool "NVMe over Fabrics In-band Authentication support" depends onNVME_TARGETdrivers/nvme/target/configfs.c +1
-0@@ -15,6 +15,7 @@ #ifdef CONFIG_NVME_TARGET_AUTH #include <linux/nvme-auth.h> #endif +#include <linux/nvme-keyring.h> #include <crypto/hash.h> #include <crypto/kpp.h>@@ -204,6 +205,14 @@ static ssize_t nvmet_addr_treq_store(struct config_item *item,found:
if (port->disc_addr.trtype==NVMF_TRTYPE_TCP) {
+ if (!IS_ENABLED(CONFIG_NVME_TARGET_TCP_TLS)) {
+pr_err("TLS is not supported\n");
+ return-EINVAL;
+ }
+ if (!port->keyring) {
+pr_err("TLS keyring not configured\n");
+ return-EINVAL;
+ }
if (port->disc_addr.tsas.tcp.sectype!=NVMF_TCP_SECTYPE_TLS13) {pr_warn("cannot change TREQ when TLS is not enabled\n"); return-EINVAL;drivers/nvme/target/configfs.c +18
-0@@ -399,6 +408,15 @@ static ssize_t nvmet_addr_tsas_store(struct config_item *item, if (port->disc_addr.trtype != NVMF_TRTYPE_TCP) return -EINVAL; + if (!IS_ENABLED(CONFIG_NVME_TARGET_TCP_TLS)) { + pr_err("TLS is not supported\n"); + return -EINVAL; + } + if (!port->keyring) { + pr_err("TLS keyring not configured\n"); + return -EINVAL; + } + for (i = 0; i < ARRAY_SIZE(nvmet_addr_tsas_tcp); i++) { if (sysfs_streq(page, nvmet_addr_tsas_tcp[i].name)) goto found;@@ -1825,6 +1843,7 @@ static void nvmet_port_release(struct config_item *item) flush_workqueue(nvmet_wq); list_del(&port->global_entry); + key_put(port->keyring); kfree(port->ana_state); kfree(port); }@@ -1874,6 +1893,14 @@ static struct config_group *nvmet_ports_make(struct config_group *group, return ERR_PTR(-ENOMEM); } + if (nvme_keyring_id()) { + port->keyring = key_lookup(nvme_keyring_id()); + if (IS_ERR(port->keyring)) { + pr_warn("NVMe keyring not available, disabling TLS\n"); + port->keyring = NULL; + } + } + for (i = 1; i <= NVMET_MAX_ANAGRPS; i++) { if (i == NVMET_DEFAULT_ANA_GRPID) port->ana_state[1] = NVME_ANA_OPTIMIZED;drivers/nvme/target/nvmet.h +1
-0@@ -158,6 +158,7 @@ struct nvmet_port { struct config_group ana_groups_group; struct nvmet_ana_group ana_default_group; enum nvme_ana_state *ana_state; + struct key *keyring; void *priv; bool enabled; int inline_data_size;drivers/nvme/target/tcp.c +6
-0@@ -8,9 +8,13 @@ #include <linux/init.h> #include <linux/slab.h> #include <linux/err.h> +#include <linux/key.h> #include <linux/nvme-tcp.h> +#include <linux/nvme-keyring.h> #include <net/sock.h> #include <net/tcp.h> +#include <net/tls.h> +#include <net/handshake.h> #include <linux/inet.h> #include <linux/llist.h> #include <crypto/hash.h>@@ -66,6 +70,16 @@ device_param_cb(idle_poll_period_usecs, &set_param_ops, MODULE_PARM_DESC(idle_poll_period_usecs, "nvmet tcp io_work poll till idle time period in usecs: Default 0"); +#ifdef CONFIG_NVME_TARGET_TCP_TLS +/*
Quoted 9 lines
drivers/nvme/target/tcp.c device_param_cb(idle_poll_period_usecs, &set_param_ops, · line 80
Quoted 6 lines
drivers/nvme/target/tcp.c +6
-0+* TLS handshake timeout +*/ +static int tls_handshake_timeout =10 ; +module_param (tls_handshake_timeout, int,0644 ); +MODULE_PARM_DESC (tls_handshake_timeout, + "nvme TLS handshake timeout in seconds (default 30)");modparam description is lying...
Yeah, don't trust it :-)
Quoted 67 lines
Quoted 67 lines
drivers/nvme/target/tcp.c +30
-4+#endif + #define NVMET_TCP_RECV_BUDGET 8 #define NVMET_TCP_SEND_BUDGET 8 #define NVMET_TCP_IO_WORK_BUDGET 64@@ -122,6 +136,7 @@ struct nvmet_tcp_cmd { enum nvmet_tcp_queue_state { NVMET_TCP_Q_CONNECTING, + NVMET_TCP_Q_TLS_HANDSHAKE, NVMET_TCP_Q_LIVE, NVMET_TCP_Q_DISCONNECTING, };@@ -154,6 +169,8 @@ struct nvmet_tcp_queue { bool data_digest; struct ahash_request *snd_hash; struct ahash_request *rcv_hash; + key_serial_t tls_pskid; + struct delayed_work tls_handshake_work; unsigned long poll_end;@@ -1285,12 +1302,12 @@ static int nvmet_tcp_try_recv(structnvmet_tcp_queue *queue, static void nvmet_tcp_schedule_release_queue(struct nvmet_tcp_queue *queue) { - spin_lock(&queue->state_lock); + spin_lock_irq(&queue->state_lock); if (queue->state != NVMET_TCP_Q_DISCONNECTING) { queue->state = NVMET_TCP_Q_DISCONNECTING; queue_work(nvmet_wq, &queue->release_work); } - spin_unlock(&queue->state_lock); + spin_unlock_irq(&queue->state_lock); } static inline void nvmet_tcp_arm_queue_deadline(struct nvmet_tcp_queue *queue)@@ -1512,8 +1529,12 @@ static void nvmet_tcp_data_ready(struct sock *sk) read_lock_bh(&sk->sk_callback_lock); queue = sk->sk_user_data; - if (likely(queue)) - queue_work_on(queue_cpu(queue), nvmet_tcp_wq, &queue->io_work); + if (queue->data_ready) + queue->data_ready(sk); + if (likely(queue) && + queue->state != NVMET_TCP_Q_TLS_HANDSHAKE) + queue_work_on(queue_cpu(queue), nvmet_tcp_wq, + &queue->io_work); read_unlock_bh(&sk->sk_callback_lock); }@@ -1621,6 +1642,75 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) return ret; } +#ifdef CONFIG_NVME_TARGET_TCP_TLS +static void nvmet_tcp_tls_handshake_done (void *data,int status, + key_serial_t peerid) +{ + struct nvmet_tcp_queue *queue = data; + + pr_debug("queue %d: TLS handshake done, key %x, status %d\n", + queue->idx, peerid, status); + spin_lock_irq(&queue->state_lock); + if (queue->state != NVMET_TCP_Q_TLS_HANDSHAKE) { + pr_warn("queue %d: TLS handshake already completed\n", + queue->idx); + spin_unlock_irq(&queue->state_lock); + return; + } + if (!status) + queue->tls_pskid = peerid;
Quoted 9 lines
drivers/nvme/target/tcp.c static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) · line 1666
Quoted 5 lines
drivers/nvme/target/tcp.c +5
-0+ queue->state = NVMET_TCP_Q_CONNECTING; + spin_unlock_irq(&queue->state_lock); + + cancel_delayed_work_sync(&queue->tls_handshake_work); + if (status) {I think that after this call, you cannot reference anything in queue as it may have been released. Or I'm missing something?
I guess I can, as this code is gated by the state change above. Once we are here the state has been updated, so the timeout work will short circuit and not delete the queue.
Cheers,
Hannes
Sagi Grimberg
maintainerRe: [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall
Quoted 31 lines
Quoted 22 lines
Quoted 22 lines
drivers/nvme/target/tcp.c +17
-0@@ -1621,6 +1642,75 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) return ret; } +#ifdef CONFIG_NVME_TARGET_TCP_TLS +static void nvmet_tcp_tls_handshake_done (void *data,int status, + key_serial_t peerid) +{ + struct nvmet_tcp_queue *queue = data; + + pr_debug("queue %d: TLS handshake done, key %x, status %d\n", + queue->idx, peerid, status); + spin_lock_irq(&queue->state_lock); + if (queue->state != NVMET_TCP_Q_TLS_HANDSHAKE) { + pr_warn("queue %d: TLS handshake already completed\n", + queue->idx); + spin_unlock_irq(&queue->state_lock); + return; + } + if (!status) + queue->tls_pskid = peerid;Quoted 9 lines
drivers/nvme/target/tcp.c static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) · line 1666
Quoted 5 lines
drivers/nvme/target/tcp.c +5
-0+ queue->state = NVMET_TCP_Q_CONNECTING; + spin_unlock_irq(&queue->state_lock); + + cancel_delayed_work_sync(&queue->tls_handshake_work); + if (status) {I think that after this call, you cannot reference anything in queue as it may have been released. Or I'm missing something?
Quoted 3 lines
I guess I can, as this code is gated by the state change above. Once we are here the state has been updated, so the timeout work will short circuit and not delete the queue.
But who guarantees that queue->state_lock is a valid dereference?
Sagi Grimberg
maintainerRe: [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall
Quoted 31 lines · Sagi Grimberg
Quoted 31 lines
Quoted 31 lines
Quoted 17 lines
drivers/nvme/target/tcp.c +12
-0@@ -1621,6 +1642,75 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) return ret; } +#ifdef CONFIG_NVME_TARGET_TCP_TLS +static void nvmet_tcp_tls_handshake_done (void *data,int status, + key_serial_t peerid) +{ + struct nvmet_tcp_queue *queue = data; + + pr_debug("queue %d: TLS handshake done, key %x, status %d\n", + queue->idx, peerid, status); + spin_lock_irq(&queue->state_lock); + if (queue->state != NVMET_TCP_Q_TLS_HANDSHAKE) { + pr_warn("queue %d: TLS handshake already completed\n", + queue->idx);drivers/nvme/target/tcp.c static int nvmet_tcp_set_queue_sock(struct · line 1666
Quoted 10 lines
drivers/nvme/target/tcp.c +10
-0+ spin_unlock_irq(&queue->state_lock); + return; + } + if (!status) + queue->tls_pskid = peerid; + queue->state = NVMET_TCP_Q_CONNECTING; + spin_unlock_irq(&queue->state_lock); + + cancel_delayed_work_sync(&queue->tls_handshake_work); + if (status) {I think that after this call, you cannot reference anything in queue as it may have been released. Or I'm missing something?
Quoted 5 lines
Quoted 3 lines
I guess I can, as this code is gated by the state change above. Once we are here the state has been updated, so the timeout work will short circuit and not delete the queue.
But who guarantees that
queue->state_lockis a valid dereference?
The lock acquired in the first line of the function...
I think we need a reference count here...
Re: [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall
Quoted 38 lines · Sagi Grimberg
Quoted 35 lines · Sagi Grimberg
Quoted 34 lines
Quoted 22 lines
Quoted 22 lines
drivers/nvme/target/tcp.c +17
-0@@ -1621,6 +1642,75 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) return ret; } +#ifdef CONFIG_NVME_TARGET_TCP_TLS +static void nvmet_tcp_tls_handshake_done (void *data,int status, + key_serial_t peerid) +{ + struct nvmet_tcp_queue *queue = data; + + pr_debug("queue %d: TLS handshake done, key %x, status %d\n", + queue->idx, peerid, status); + spin_lock_irq(&queue->state_lock); + if (queue->state != NVMET_TCP_Q_TLS_HANDSHAKE) { + pr_warn("queue %d: TLS handshake already completed\n", + queue->idx); + spin_unlock_irq(&queue->state_lock); + return; + } + if (!status) + queue->tls_pskid = peerid;Quoted 9 lines
drivers/nvme/target/tcp.c static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) · line 1666
Quoted 5 lines
drivers/nvme/target/tcp.c +5
-0+ queue->state = NVMET_TCP_Q_CONNECTING; + spin_unlock_irq(&queue->state_lock); + + cancel_delayed_work_sync(&queue->tls_handshake_work); + if (status) {I think that after this call, you cannot reference anything in queue as it may have been released. Or I'm missing something?
I guess I can, as this code is gated by the state change above. Once we are here the state has been updated, so the timeout work will short circuit and not delete the queue.
Quoted 5 lines
Quoted 1 line
But who guarantees that
queue->state_lockis a valid dereference?The lock acquired in the first line of the function...
I think we need a reference count here...
Or use:
static void nvmet_tcp_schedule_release_queue(struct nvmet_tcp_queue *queue)
{
spin_lock_irq(&queue->state_lock);
if (queue->state != NVMET_TCP_Q_TLS_HANDSHAKE &&
queue->state != NVMET_TCP_Q_DISCONNECTING) {
queue->state = NVMET_TCP_Q_DISCONNECTING;
queue_work(nvmet_wq, &queue->release_work);
}
spin_unlock_irq(&queue->state_lock);
}Such that release_queue will be ignored when a socket state change happens while handshake is in progress.
Handshake will complete with done or timeout, both of which will call schedule_release_queue() (with the corrrect state) on error.
Cheers,
Hannes
Re: [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall
In reply to Sagi GrimbergQuoted 31 lines · Sagi Grimberg
Quoted 31 lines
Quoted 31 lines
Quoted 17 lines
drivers/nvme/target/tcp.c +12
-0@@ -1621,6 +1642,75 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue) return ret; } +#ifdef CONFIG_NVME_TARGET_TCP_TLS +static void nvmet_tcp_tls_handshake_done (void *data,int status, + key_serial_t peerid) +{ + struct nvmet_tcp_queue *queue = data; + + pr_debug("queue %d: TLS handshake done, key %x, status %d\n", + queue->idx, peerid, status); + spin_lock_irq(&queue->state_lock); + if (queue->state != NVMET_TCP_Q_TLS_HANDSHAKE) { + pr_warn("queue %d: TLS handshake already completed\n", + queue->idx);drivers/nvme/target/tcp.c static int nvmet_tcp_set_queue_sock(struct · line 1666
Quoted 10 lines
drivers/nvme/target/tcp.c +10
-0+ spin_unlock_irq(&queue->state_lock); + return; + } + if (!status) + queue->tls_pskid = peerid; + queue->state = NVMET_TCP_Q_CONNECTING; + spin_unlock_irq(&queue->state_lock); + + cancel_delayed_work_sync(&queue->tls_handshake_work); + if (status) {I think that after this call, you cannot reference anything in queue as it may have been released. Or I'm missing something?
Quoted 5 lines
Quoted 3 lines
I guess I can, as this code is gated by the state change above. Once we are here the state has been updated, so the timeout work will short circuit and not delete the queue.
But who guarantees that
queue->state_lockis a valid dereference?
Ah, right. Will be fixing it up.
Cheers,
Hannes
Re: [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall
In reply to Sagi GrimbergQuoted 12 lines · Sagi Grimberg
Quoted 6 lines · Hannes Reinecke
Add functions to start the TLS handshake upcall when the TCP TSAS sectype is set to 'tls1.3' and add a config option
NVME_TARGET_TCP_TLS.
And move the 'state' lock to an irq-safe lock as the 'done' callback from the TLS handshake will be running in interrupt context.Really.. that is surprising. Can you describe how exactly?
Ho-hum. Yes, I can, and it seems to be related to my test setup.
I'm running nvme and nvmet over the loopback interface, and with thatnvme_tcp_stop_queue() induces a softirq triggering a socket state change
on the target.
Which means that nvmet_tcp_schedule_release_queue() is called from softirq, triggering the spin_lock warning. Probably warrants a separate patch, though.
Cheers,
Hannes
Signature · 5 lines
Dr. Hannes Reinecke Kernel Storage Architect [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
Sagi Grimberg
maintainerRe: [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall
Quoted 9 lines
Quoted 9 lines · Hannes Reinecke
Quoted 6 lines
Add functions to start the TLS handshake upcall when the TCP TSAS sectype is set to 'tls1.3' and add a config option
NVME_TARGET_TCP_TLS.
And move the 'state' lock to an irq-safe lock as the 'done' callback from the TLS handshake will be running in interrupt context.
Quoted 8 lines
Quoted 2 lines
Really.. that is surprising. Can you describe how exactly?
Ho-hum. Yes, I can, and it seems to be related to my test setup.
I'm running nvme and nvmet over the loopback interface, and with thatnvme_tcp_stop_queue()induces a softirq triggering a socket state change
on the target.
Which means thatnvmet_tcp_schedule_release_queue()is called from softirq, triggering thespin_lockwarning. Probably warrants a separate patch, though.
If this is driven from the network stack, it should be spin_lock_bh.
And yes, this is a separate patch, and probably with a fixes tag, and preferably separate from the patch set because this is an unrelated fix.
PATCH v6 16/16 nvmet-tcp: control messages for recvmsg()
In reply to Hannes ReineckekTLS requires control messages for recvmsg() to relay any out-of-band TLS messages (eg TLS alerts) to the caller.
--- drivers/nvme/target/tcp.c | 83 +++++++++++++++++++++++++++++++++------ 1 file changed, 72 insertions(+), 11 deletions(-)
drivers/nvme/target/tcp.c +72 -11
@@ -14,6 +14,7 @@#include <net/sock.h> #include <net/tcp.h> #include <net/tls.h> +#include <net/tls_prot.h> #include <net/handshake.h> #include <linux/inet.h> #include <linux/llist.h>
@@ -70,6 +71,9 @@ device_param_cb(idle_poll_period_usecs, &set_param_ops,MODULE_PARM_DESC (idle_poll_period_usecs,"nvmet tcp io_work poll till idle time period in usecs: Default 0" ); +#define nvmet_queue_is_tls (queue) \ + ((queue)->port->nport->disc_addr.tsas.tcp.sectype == NVMF_TCP_SECTYPE_TLS13) +#ifdef CONFIG_NVME_TARGET_TCP_TLS /* * TLS handshake timeout
@@ -118,6 +122,7 @@ struct nvmet_tcp_cmd {u32 pdu_len;u32 pdu_recv;int sg_idx; +char recv_cbuf[CMSG_LEN (sizeof (char ))];struct msghdr recv_msg;struct bio_vec *iov;u32 flags;
@@ -1116,20 +1121,59 @@ static inline bool nvmet_tcp_pdu_valid(u8 type)return false; } +static int nvmet_tcp_tls_record_ok (struct nvmet_tcp_queue *queue, +struct msghdr *msg,char *cbuf) +{ +struct cmsghdr *cmsg = (struct cmsghdr *)cbuf; +u8 ctype, level, description; +int ret =0 ; + +if (!nvmet_queue_is_tls (queue)) +return 0 ; + + ctype =tls_get_record_type (queue->sock->sk, cmsg); +switch (ctype) { +case 0 : +break ; +case TLS_RECORD_TYPE_DATA : +break ; +case TLS_RECORD_TYPE_ALERT : +tls_alert_recv (queue->sock->sk, msg, &level, &description); +pr_err ("TLS Alert level %u desc %u\n" , level, description); + ret = (level ==TLS_ALERT_LEVEL_FATAL ) ? + -ENOTCONN : -EAGAIN ; +break ; +default : +/* discard this record type */ +pr_err ("TLS record %d unhandled\n" , ctype); + ret = -EAGAIN ; +break ; + } +return ret; +} +static int nvmet_tcp_try_recv_pdu (struct nvmet_tcp_queue *queue) {struct nvme_tcp_hdr *hdr = &queue->pdu.cmd.hdr; -int len; +int len, ret;struct kvec iov; +char cbuf[CMSG_LEN (sizeof (char ))] = {};struct msghdr msg = { .msg_flags =MSG_DONTWAIT }; recv: iov.iov_base = (void *)&queue->pdu + queue->offset; iov.iov_len = queue->left; +if (nvmet_queue_is_tls (queue)) { + msg.msg_control = cbuf; + msg.msg_controllen =sizeof (cbuf); + } len =kernel_recvmsg (queue->sock, &msg, &iov,1 , iov.iov_len, msg.msg_flags);if (unlikely (len <0 ))return len; + ret =nvmet_tcp_tls_record_ok (queue, &msg, cbuf); +if (ret <0 ) +return ret; queue->offset += len; queue->left -= len;
@@ -1182,16 +1226,21 @@ static void nvmet_tcp_prep_recv_ddgst(struct nvmet_tcp_cmd *cmd)static int nvmet_tcp_try_recv_data (struct nvmet_tcp_queue *queue) {struct nvmet_tcp_cmd *cmd = queue->cmd; -int ret; +int len, ret;while (msg_data_left (&cmd->recv_msg)) { - ret =sock_recvmsg (cmd->queue->sock, &cmd->recv_msg, + len =sock_recvmsg (cmd->queue->sock, &cmd->recv_msg, cmd->recv_msg.msg_flags); -if (ret <=0 ) +if (len <=0 ) +return len; + ret =nvmet_tcp_tls_record_ok (cmd->queue, + &cmd->recv_msg, + cmd->recv_cbuf); +if (ret <0 )return ret; - cmd->pdu_recv += ret; - cmd->rbytes_done += ret; + cmd->pdu_recv += len; + cmd->rbytes_done += len; }if (queue->data_digest) {
@@ -1209,20 +1258,28 @@ static int nvmet_tcp_try_recv_data(struct nvmet_tcp_queue *queue)static int nvmet_tcp_try_recv_ddgst (struct nvmet_tcp_queue *queue) {struct nvmet_tcp_cmd *cmd = queue->cmd; -int ret; +int ret, len; +char cbuf[CMSG_LEN (sizeof (char ))] = {};struct msghdr msg = { .msg_flags =MSG_DONTWAIT };struct kvec iov = { .iov_base = (void *)&cmd->recv_ddgst + queue->offset, .iov_len = queue->left }; - ret =kernel_recvmsg (queue->sock, &msg, &iov,1 , +if (nvmet_queue_is_tls (queue)) { + msg.msg_control = cbuf; + msg.msg_controllen =sizeof (cbuf); + } + len =kernel_recvmsg (queue->sock, &msg, &iov,1 , iov.iov_len, msg.msg_flags); -if (unlikely (ret <0 )) +if (unlikely (len <0 )) +return len; + ret =nvmet_tcp_tls_record_ok (queue, &msg, cbuf); +if (ret <0 )return ret; - queue->offset += ret; - queue->left -= ret; + queue->offset += len; + queue->left -= len;if (queue->left)return -EAGAIN ;
@@ -1389,6 +1446,10 @@ static int nvmet_tcp_alloc_cmd(struct nvmet_tcp_queue *queue,if (!c->r2t_pdu) goto out_free_data; +if (nvmet_queue_is_tls (queue)) { + c->recv_msg.msg_control = c->recv_cbuf; + c->recv_msg.msg_controllen =sizeof (c->recv_cbuf); + } c->recv_msg.msg_flags =MSG_DONTWAIT |MSG_NOSIGNAL ;list_add_tail (&c->entry, &queue->free_list);
Signature · 1 line
2.35.3
Sagi Grimberg
maintainerRe: [PATCH 16/16] nvmet-tcp: control messages for recvmsg()
Quoted 21 lines · Hannes Reinecke
kTLS requires control messages for
recvmsg()to relay any out-of-band TLS messages (eg TLS alerts) to the caller.Signed-off-by Hannes Reinecke <[email protected]>--- drivers/nvme/target/tcp.c | 83 +++++++++++++++++++++++++++++++++------ 1 file changed, 72 insertions(+), 11 deletions(-)drivers/nvme/target/tcp.c +1
-0@@ -14,6 +14,7 @@#include <net/sock.h> #include <net/tcp.h> #include <net/tls.h> +#include <net/tls_prot.h> #include <net/handshake.h> #include <linux/inet.h> #include <linux/llist.h>
drivers/nvme/target/tcp.c device_param_cb(idle_poll_period_usecs, &set_param_ops, · line 75
Quoted 5 lines
drivers/nvme/target/tcp.c +2
-0@@ -70,6 +71,9 @@ device_param_cb(idle_poll_period_usecs, &set_param_ops,MODULE_PARM_DESC (idle_poll_period_usecs,"nvmet tcp io_work poll till idle time period in usecs: Default 0" ); +#define nvmet_queue_is_tls (queue) \ + ((queue)->port->nport->disc_addr.tsas.tcp.sectype == NVMF_TCP_SECTYPE_TLS13)
That is some steep dereferencing... I'd say just cache a flag in the queue itself, or in the port.
Quoted 80 lines
drivers/nvme/target/tcp.c +43
-2+#ifdef CONFIG_NVME_TARGET_TCP_TLS /* * TLS handshake timeout @@ -118,6 +122,7 @@ struct nvmet_tcp_cmd {u32 pdu_len;u32 pdu_recv;int sg_idx; +char recv_cbuf[CMSG_LEN (sizeof (char ))];struct msghdr recv_msg;struct bio_vec *iov;u32 flags;@@ -1116,20 +1121,59 @@ static inline bool nvmet_tcp_pdu_valid(u8 type)return false; } +static int nvmet_tcp_tls_record_ok (struct nvmet_tcp_queue *queue, +struct msghdr *msg,char *cbuf) +{ +struct cmsghdr *cmsg = (struct cmsghdr *)cbuf; +u8 ctype, level, description; +int ret =0 ; + +if (!nvmet_queue_is_tls (queue)) +return 0 ; + + ctype =tls_get_record_type (queue->sock->sk, cmsg); +switch (ctype) { +case 0 : +break ; +case TLS_RECORD_TYPE_DATA : +break ; +case TLS_RECORD_TYPE_ALERT : +tls_alert_recv (queue->sock->sk, msg, &level, &description); +pr_err ("TLS Alert level %u desc %u\n" , level, description); + ret = (level ==TLS_ALERT_LEVEL_FATAL ) ? + -ENOTCONN : -EAGAIN ; +break ; +default : +/* discard this record type */ +pr_err ("TLS record %d unhandled\n" , ctype); + ret = -EAGAIN ; +break ; + } +return ret; +} +static int nvmet_tcp_try_recv_pdu (struct nvmet_tcp_queue *queue) {struct nvme_tcp_hdr *hdr = &queue->pdu.cmd.hdr; -int len; +int len, ret;struct kvec iov; +char cbuf[CMSG_LEN (sizeof (char ))] = {};struct msghdr msg = { .msg_flags =MSG_DONTWAIT }; recv: iov.iov_base = (void *)&queue->pdu + queue->offset; iov.iov_len = queue->left; +if (nvmet_queue_is_tls (queue)) { + msg.msg_control = cbuf; + msg.msg_controllen =sizeof (cbuf); + } len =kernel_recvmsg (queue->sock, &msg, &iov,1 , iov.iov_len, msg.msg_flags);if (unlikely (len <0 ))return len; + ret =nvmet_tcp_tls_record_ok (queue, &msg, cbuf); +if (ret <0 ) +return ret; queue->offset += len; queue->left -= len;@@ -1182,16 +1226,21 @@ static void nvmet_tcp_prep_recv_ddgst(struct nvmet_tcp_cmd *cmd)static int nvmet_tcp_try_recv_data (struct nvmet_tcp_queue *queue) {struct nvmet_tcp_cmd *cmd = queue->cmd; -int ret; +int len, ret;
drivers/nvme/target/tcp.c static void nvmet_tcp_prep_recv_ddgst(struct nvmet_tcp_cmd *cmd) · line 1238
Quoted 10 lines
drivers/nvme/target/tcp.c +6
-2while (msg_data_left (&cmd->recv_msg)) { - ret =sock_recvmsg (cmd->queue->sock, &cmd->recv_msg, + len =sock_recvmsg (cmd->queue->sock, &cmd->recv_msg, cmd->recv_msg.msg_flags); -if (ret <=0 ) +if (len <=0 ) +return len; + ret =nvmet_tcp_tls_record_ok (cmd->queue, + &cmd->recv_msg, + cmd->recv_cbuf);
I think it will be better to condition on tls on the call sites, so it will be clearer that we are checking the tls record only for tls queues.
Re: [PATCH 16/16] nvmet-tcp: control messages for recvmsg()
Quoted 24 lines · Sagi Grimberg
Quoted 21 lines · Hannes Reinecke
kTLS requires control messages for
recvmsg()to relay any out-of-band TLS messages (eg TLS alerts) to the caller.Signed-off-by Hannes Reinecke <[email protected]>---
drivers/nvme/target/tcp.c| 83 +++++++++++++++++++++++++++++++++------1 file changed, 72 insertions(+), 11 deletions(-)drivers/nvme/target/tcp.c +1
-0@@ -14,6 +14,7 @@ #include <net/sock.h> #include <net/tcp.h> #include <net/tls.h> +#include <net/tls_prot.h> #include <net/handshake.h> #include <linux/inet.h> #include <linux/llist.h>@@ -70,6 +71,9 @@ device_param_cb(idle_poll_period_usecs, &set_param_ops,
Quoted 9 lines
drivers/nvme/target/tcp.c device_param_cb(idle_poll_period_usecs, &set_param_ops,
Quoted 5 lines
drivers/nvme/target/tcp.c +2
-0MODULE_PARM_DESC(idle_poll_period_usecs, "nvmet tcp io_work poll till idle time period in usecs: Default 0"); +#define nvmet_queue_is_tls (queue) \ + ((queue)->port->nport->disc_addr.tsas.tcp.sectype == NVMF_TCP_SECTYPE_TLS13)That is some steep dereferencing... I'd say just cache a flag in the queue itself, or in the port.
Yeah, not happy with that one, either.
Will be adding a queue flag.
Quoted 83 lines
Quoted 83 lines
drivers/nvme/target/tcp.c +35
-1+ #ifdef CONFIG_NVME_TARGET_TCP_TLS /** TLS handshake timeout @@ -118,6 +122,7 @@ struct nvmet_tcp_cmd { u32 pdu_len; u32 pdu_recv; int sg_idx; + char recv_cbuf[CMSG_LEN(sizeof(char))]; struct msghdr recv_msg; struct bio_vec *iov; u32 flags;@@ -1116,20 +1121,59 @@ static inline bool nvmet_tcp_pdu_valid(u8 type) return false; } +static int nvmet_tcp_tls_record_ok (struct nvmet_tcp_queue *queue, + struct msghdr *msg, char *cbuf) +{ + struct cmsghdr *cmsg = (struct cmsghdr *)cbuf; + u8 ctype, level, description; + int ret = 0; + + if (!nvmet_queue_is_tls(queue)) + return 0; + + ctype = tls_get_record_type(queue->sock->sk, cmsg); + switch (ctype) { + case 0: + break; + case TLS_RECORD_TYPE_DATA: + break; + case TLS_RECORD_TYPE_ALERT: + tls_alert_recv(queue->sock->sk, msg, &level, &description); + pr_err("TLS Alert level %u desc %u\n", level, description); + ret = (level == TLS_ALERT_LEVEL_FATAL) ? + -ENOTCONN : -EAGAIN; + break; + default: + /* discard this record type */ + pr_err("TLS record %d unhandled\n", ctype); + ret = -EAGAIN; + break; + } + return ret; +} + static int nvmet_tcp_try_recv_pdu(struct nvmet_tcp_queue *queue) { struct nvme_tcp_hdr *hdr = &queue->pdu.cmd.hdr; - int len; + int len, ret; struct kvec iov; + char cbuf[CMSG_LEN(sizeof(char))] = {}; struct msghdr msg = { .msg_flags = MSG_DONTWAIT };recv:
iov.iov_base = (void *)&queue->pdu +queue->offset; iov.iov_len =queue->left;
+ if (nvmet_queue_is_tls(queue)) {
+ msg.msg_control = cbuf;
+ msg.msg_controllen = sizeof(cbuf);
+ }
len =kernel_recvmsg(queue->sock, &msg, &iov, 1, iov.iov_len, msg.msg_flags);
if (unlikely(len < 0))
return len;
+ ret =nvmet_tcp_tls_record_ok(queue, &msg, cbuf); + if (ret < 0)
+ return ret;
queue->offset+= len;
queue->left-= len;drivers/nvme/target/tcp.c +3
-3@@ -1182,16 +1226,21 @@ static void nvmet_tcp_prep_recv_ddgst(struct nvmet_tcp_cmd *cmd) static int nvmet_tcp_try_recv_data(struct nvmet_tcp_queue *queue) { struct nvmet_tcp_cmd *cmd = queue->cmd; - int ret; + int len, ret; while (msg_data_left(&cmd->recv_msg)) { - ret = sock_recvmsg(cmd->queue->sock, &cmd->recv_msg, + len = sock_recvmsg(cmd->queue->sock, &cmd->recv_msg, cmd->recv_msg.msg_flags); - if (ret <= 0) + if (len <= 0)
Quoted 8 lines
drivers/nvme/target/tcp.c static void nvmet_tcp_prep_recv_ddgst(struct nvmet_tcp_cmd *cmd) · line 1238
Quoted 4 lines
drivers/nvme/target/tcp.c +4
-0+ return len; + ret = nvmet_tcp_tls_record_ok(cmd->queue, + &cmd->recv_msg, + cmd->recv_cbuf);I think it will be better to condition on tls on the call sites, so it will be clearer that we are checking the tls record only for tls queues.
Ok, will be doing that.
Cheers,
Hannes