From: Sagi Grimberg <sagi@grimberg.me>
To: Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org,
Chuck Lever <chuck.lever@oracle.com>,
kernel-tls-handshake@lists.linux.dev
Subject: Re: [PATCH 17/18] nvmet-tcp: control messages for recvmsg()
Date: Mon, 3 Apr 2023 15:59:27 +0300 [thread overview]
Message-ID: <ef8a32b6-aa9d-c0a4-df77-2636d35efb9f@grimberg.me> (raw)
In-Reply-To: <20230329135938.46905-18-hare@suse.de>
On 3/29/23 16:59, Hannes Reinecke wrote:
> 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 <hare@suse.de>
> ---
> drivers/nvme/target/tcp.c | 71 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 71 insertions(+)
>
> diff --git a/drivers/nvme/target/tcp.c b/drivers/nvme/target/tcp.c
> index 5daf16138471..75017fd5da9f 100644
> --- a/drivers/nvme/target/tcp.c
> +++ b/drivers/nvme/target/tcp.c
> @@ -12,6 +12,7 @@
> #include <net/sock.h>
> #include <net/tcp.h>
> #ifdef CONFIG_NVME_TLS
> +#include <net/tls.h>
> #include <net/handshake.h>
> #include <linux/nvme-keyring.h>
> #endif
> @@ -92,6 +93,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;
> @@ -1086,7 +1088,18 @@ static int nvmet_tcp_try_recv_pdu(struct nvmet_tcp_queue *queue)
> struct nvme_tcp_hdr *hdr = &queue->pdu.cmd.hdr;
> int len;
> struct kvec iov;
> +#ifdef CONFIG_NVME_TLS
Do you need this ifdef? The recv_cbuf in the cmd is not under and ifdef.
> + char cbuf[CMSG_LEN(sizeof(char))] = {};
> + unsigned char ctype;
> + struct cmsghdr *cmsg;
> + struct msghdr msg = {
> + .msg_control = cbuf,
> + .msg_controllen = sizeof(cbuf),
> + .msg_flags = MSG_DONTWAIT
> + };
> +#else
> struct msghdr msg = { .msg_flags = MSG_DONTWAIT };
> +#endif
>
> recv:
> iov.iov_base = (void *)&queue->pdu + queue->offset;
> @@ -1095,6 +1108,19 @@ static int nvmet_tcp_try_recv_pdu(struct nvmet_tcp_queue *queue)
> iov.iov_len, msg.msg_flags);
> if (unlikely(len < 0))
> return len;
> +#ifdef CONFIG_NVME_TLS
> + cmsg = (struct cmsghdr *)cbuf;
> + if (CMSG_OK(&msg, cmsg) &&
> + cmsg->cmsg_level == SOL_TLS &&
> + cmsg->cmsg_type == TLS_GET_RECORD_TYPE) {
> + ctype = *((unsigned char *)CMSG_DATA(cmsg));
> + if (ctype != TLS_RECORD_TYPE_DATA) {
> + pr_err("queue %d unhandled TLS record %d\n",
> + queue->idx, ctype);
> + return -ENOTCONN;
> + }
> + }
> +#endif
Can we consolidate this to a helper?
Something like:
static int nvmet_tcp_check_cmsg(struct nvmet_tcp_queue *queue, struct
cmsghdr *cmsg)
{
if (!IS_ENABLED(CONFIG_NVME_TLS))
return 0;
if (CMSG_OK(&msg, cmsg) &&
cmsg->cmsg_level == SOL_TLS &&
cmsg->cmsg_type == TLS_GET_RECORD_TYPE) {
ctype = *((unsigned char *)CMSG_DATA(cmsg));
if (ctype != TLS_RECORD_TYPE_DATA) {
pr_err("queue %d unhandled TLS record %d\n",
queue->idx, ctype);
return -ENOTCONN;
}
}
return 0;
}
>
> queue->offset += len;
> queue->left -= len;
> @@ -1150,10 +1176,27 @@ static int nvmet_tcp_try_recv_data(struct nvmet_tcp_queue *queue)
> int ret;
>
> while (msg_data_left(&cmd->recv_msg)) {
> +#ifdef CONFIG_NVME_TLS
> + struct cmsghdr *cmsg;
> + unsigned char ctype;
> +#endif
> ret = sock_recvmsg(cmd->queue->sock, &cmd->recv_msg,
> cmd->recv_msg.msg_flags);
> if (ret <= 0)
> return ret;
> +#ifdef CONFIG_NVME_TLS
> + cmsg = (struct cmsghdr *)cmd->recv_cbuf;
> + if (CMSG_OK(&cmd->recv_msg, cmsg) &&
> + cmsg->cmsg_level == SOL_TLS &&
> + cmsg->cmsg_type == TLS_GET_RECORD_TYPE) {
> + ctype = *((unsigned char *)CMSG_DATA(cmsg));
> + if (ctype != TLS_RECORD_TYPE_DATA) {
> + pr_err("queue %d unhandled TLS record %d\n",
> + queue->idx, ctype);
> + return -ENOTCONN;
> + }
> + }
> +#endif
>
> cmd->pdu_recv += ret;
> cmd->rbytes_done += ret;
> @@ -1175,7 +1218,18 @@ static int nvmet_tcp_try_recv_ddgst(struct nvmet_tcp_queue *queue)
> {
> struct nvmet_tcp_cmd *cmd = queue->cmd;
> int ret;
> +#ifdef CONFIG_NVME_TLS
> + char cbuf[CMSG_LEN(sizeof(char))] = {};
> + unsigned char ctype;
> + struct cmsghdr *cmsg;
> + struct msghdr msg = {
> + .msg_control = cbuf,
> + .msg_controllen = sizeof(cbuf),
> + .msg_flags = MSG_DONTWAIT
> + };
> +#else
> struct msghdr msg = { .msg_flags = MSG_DONTWAIT };
> +#endif
> struct kvec iov = {
> .iov_base = (void *)&cmd->recv_ddgst + queue->offset,
> .iov_len = queue->left
> @@ -1185,6 +1239,19 @@ static int nvmet_tcp_try_recv_ddgst(struct nvmet_tcp_queue *queue)
> iov.iov_len, msg.msg_flags);
> if (unlikely(ret < 0))
> return ret;
> +#ifdef CONFIG_NVME_TLS
> + cmsg = (struct cmsghdr *)cbuf;
> + if (CMSG_OK(&msg, cmsg) &&
> + cmsg->cmsg_level == SOL_TLS &&
> + cmsg->cmsg_type == TLS_GET_RECORD_TYPE) {
> + ctype = *((unsigned char *)CMSG_DATA(cmsg));
> + if (ctype != TLS_RECORD_TYPE_DATA) {
> + pr_err("queue %d unhandled TLS record %d\n",
> + queue->idx, ctype);
> + return -ENOTCONN;
> + }
> + }
> +#endif
>
> queue->offset += ret;
> queue->left -= ret;
> @@ -1354,6 +1421,10 @@ static int nvmet_tcp_alloc_cmd(struct nvmet_tcp_queue *queue,
> if (!c->r2t_pdu)
> goto out_free_data;
>
> +#ifdef CONFIG_NVME_TLS
> + c->recv_msg.msg_control = c->recv_cbuf;
> + c->recv_msg.msg_controllen = sizeof(c->recv_cbuf);
> +#endif
> c->recv_msg.msg_flags = MSG_DONTWAIT | MSG_NOSIGNAL;
>
> list_add_tail(&c->entry, &queue->free_list);
next prev parent reply other threads:[~2023-04-03 12:59 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 13:59 [PATCHv2 00/18] nvme: In-kernel TLS support for TCP Hannes Reinecke
2023-03-29 13:59 ` [PATCH 01/18] nvme-keyring: register '.nvme' keyring and add CONFIG_NVME_TLS Hannes Reinecke
2023-03-29 14:49 ` Sagi Grimberg
2023-03-29 15:24 ` Hannes Reinecke
2023-03-29 15:04 ` Sagi Grimberg
2023-03-29 15:26 ` Hannes Reinecke
2023-03-30 8:53 ` Daniel Wagner
2023-03-30 14:38 ` Sagi Grimberg
2023-03-29 13:59 ` [PATCH 02/18] nvme-keyring: define a 'psk' keytype Hannes Reinecke
2023-03-29 13:59 ` [PATCH 03/18] nvme: add TCP TSAS definitions Hannes Reinecke
2023-03-29 13:59 ` [PATCH 04/18] nvme-tcp: add definitions for TLS cipher suites Hannes Reinecke
2023-03-29 13:59 ` [PATCH 05/18] net/tls: implement ->read_sock() Hannes Reinecke
2023-03-29 15:37 ` Sagi Grimberg
2023-03-29 15:41 ` Hannes Reinecke
2023-03-29 15:43 ` Sagi Grimberg
2023-03-29 15:44 ` Sagi Grimberg
2023-03-29 13:59 ` [PATCH 06/18] nvme/tcp: allocate socket file Hannes Reinecke
2023-03-29 15:57 ` Sagi Grimberg
2023-03-29 13:59 ` [PATCH 07/18] nvme-keyring: implement nvme_tls_psk_default() Hannes Reinecke
2023-03-29 15:35 ` Sagi Grimberg
2023-03-29 13:59 ` [PATCH 08/18] security/keys: export key_lookup() Hannes Reinecke
2023-03-29 13:59 ` [PATCH 09/18] nvme-tcp: enable TLS handshake upcall Hannes Reinecke
2023-03-30 12:54 ` Daniel Wagner
2023-03-30 12:59 ` Hannes Reinecke
2023-03-30 15:03 ` Sagi Grimberg
2023-03-30 17:16 ` Hannes Reinecke
2023-03-29 13:59 ` [PATCH 10/18] nvme-tcp: fixup send workflow for kTLS Hannes Reinecke
2023-03-30 15:24 ` Sagi Grimberg
2023-03-30 17:26 ` Hannes Reinecke
2023-03-31 5:49 ` Jakub Kicinski
2023-03-31 6:03 ` Hannes Reinecke
2023-04-03 12:20 ` Sagi Grimberg
2023-04-03 14:59 ` Jakub Kicinski
2023-04-03 15:51 ` Sagi Grimberg
2023-04-03 18:48 ` Jakub Kicinski
2023-04-03 22:36 ` Sagi Grimberg
2023-03-29 13:59 ` [PATCH 11/18] nvme-tcp: control message handling for recvmsg() Hannes Reinecke
2023-03-30 15:25 ` Sagi Grimberg
2023-03-29 13:59 ` [PATCH 12/18] nvme-fabrics: parse options 'keyring' and 'tls_key' Hannes Reinecke
2023-03-30 15:33 ` Sagi Grimberg
2023-03-30 17:34 ` Hannes Reinecke
2023-04-03 12:24 ` Sagi Grimberg
2023-04-03 12:36 ` Hannes Reinecke
2023-04-03 13:07 ` Sagi Grimberg
2023-04-03 14:11 ` Hannes Reinecke
2023-04-03 16:13 ` Sagi Grimberg
2023-03-29 13:59 ` [PATCH 13/18] nvmet: make TCP sectype settable via configfs Hannes Reinecke
2023-03-30 16:07 ` Sagi Grimberg
2023-03-30 17:37 ` Hannes Reinecke
2023-04-03 12:31 ` Sagi Grimberg
2023-04-03 12:43 ` Hannes Reinecke
2023-03-29 13:59 ` [PATCH 14/18] nvmet-tcp: allocate socket file Hannes Reinecke
2023-03-30 16:08 ` Sagi Grimberg
2023-03-30 17:37 ` Hannes Reinecke
2023-03-29 13:59 ` [PATCH 15/18] nvmet-tcp: enable TLS handshake upcall Hannes Reinecke
2023-04-03 12:51 ` Sagi Grimberg
2023-04-03 14:05 ` Hannes Reinecke
2023-03-29 13:59 ` [PATCH 16/18] nvmet-tcp: rework sendpage for kTLS Hannes Reinecke
2023-04-03 12:52 ` Sagi Grimberg
2023-03-29 13:59 ` [PATCH 17/18] nvmet-tcp: control messages for recvmsg() Hannes Reinecke
2023-04-03 12:59 ` Sagi Grimberg [this message]
2023-03-29 13:59 ` [PATCH 18/18] nvmet-tcp: add configfs attribute 'param_keyring' Hannes Reinecke
2023-04-03 13:03 ` Sagi Grimberg
2023-04-03 14:13 ` Hannes Reinecke
2023-04-03 15:53 ` Sagi Grimberg
2023-04-14 10:30 ` Hannes Reinecke
2023-04-17 13:50 ` Sagi Grimberg
2023-04-17 14:01 ` Hannes Reinecke
2023-04-17 15:12 ` Sagi Grimberg
-- strict thread matches above, loose matches on Subject: below --
2023-04-17 13:02 [PATCHv3 00/18] nvme: In-kernel TLS support for TCP Hannes Reinecke
2023-04-17 13:03 ` [PATCH 17/18] nvmet-tcp: control messages for recvmsg() Hannes Reinecke
2023-03-21 12:43 [RFC PATCH 00/18] nvme: In-kernel TLS support for TCP Hannes Reinecke
2023-03-21 12:43 ` [PATCH 17/18] nvmet-tcp: control messages for recvmsg() Hannes Reinecke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef8a32b6-aa9d-c0a4-df77-2636d35efb9f@grimberg.me \
--to=sagi@grimberg.me \
--cc=chuck.lever@oracle.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=linux-nvme@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).