public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 08/16] nvme-tcp: enable TLS handshake upcall
Date: Wed, 9 Aug 2023 12:00:40 +0200	[thread overview]
Message-ID: <113ae2a5-c5f7-3c1f-4bc7-e6db9681eb3f@suse.de> (raw)
In-Reply-To: <8f7dd2b5-bc7d-5c2f-a807-ee18e809b3a7@grimberg.me>

On 8/9/23 11:47, Sagi Grimberg wrote:
> 
>> @@ -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.

>> +        }
>> +        pskid = key_serial(ctrl->tls_key);
>> +    }
> 
> newline missing.
> 
> key_serial can operate on null.
> 
>>       for (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)
> -- 
> 
Yeah, might be simpler. I'll give it a go.

Cheers,

Hannes



  reply	other threads:[~2023-08-09 10:00 UTC|newest]

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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=113ae2a5-c5f7-3c1f-4bc7-e6db9681eb3f@suse.de \
    --to=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox