[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADUfDZp5E-oc+ikHQxvFyR7nLPWiOjqKQudC04roarn5ps9w1A@mail.gmail.com>
Date: Mon, 10 Feb 2025 09:24:54 -0800
From: Caleb Sander <csander@...estorage.com>
To: Hannes Reinecke <hare@...e.de>
Cc: Sagi Grimberg <sagi@...mberg.me>, Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@....de>, Maurizio Lombardi <mlombard@...hat.com>, linux-nvme@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] nvme-tcp: fix connect failure on receiving partial
ICResp PDU
Gentle ping on this patch. Sagi reviewed it, and I don't hear any
additional comments from Hannes.
Thanks,
Caleb
On Tue, Feb 4, 2025 at 2:20 PM Caleb Sander <csander@...estorage.com> wrote:
>
> On Sun, Feb 2, 2025 at 11:20 PM Hannes Reinecke <hare@...e.de> wrote:
> ...
> > The PSK identification has to contain the host NQN _and_ the target NQN.
> > So you need to call gen-tls-key with both in order to generate a PSK
> > with an identitify which can be found for a connection attempt.
>
> Got it. With "--hostnqn `cat /etc/nvme/hostnqn`" added to the nvme
> gen-tls-key commands, the discovery and connection succeed. I see the
> same behavior with and without my patch.
>
> $ nvme connect-all --transport tcp --traddr 127.0.0.1 --trsvcid 4420 --tls
> $ nvme list
> Node Generic SN Model
> Namespace Usage
> Format FW Rev
> --------------------- --------------------- --------------------
> ---------------------------------------- ----------
> -------------------------- ---------------- --------
> /dev/nvme1n1 /dev/ng1n1 d95671fe6e0ebf8c199c Linux
> 0x1 268.44 GB / 268.44 GB
> 512 B + 0 B 5.14.0-5
>
> Hannes, is there any other information you need or do you think this
> patch can be merged?
>
> Thanks,
> Caleb
Powered by blists - more mailing lists