[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a83f1c78-8fb8-456b-949a-6ed0b71bd7ff@suse.de>
Date: Mon, 15 Sep 2025 17:55:53 +0200
From: Hannes Reinecke <hare@...e.de>
To: Keith Busch <kbusch@...nel.org>, Olga Kornievskaia <aglo@...ch.edu>
Cc: Olga Kornievskaia <okorniev@...hat.com>, chuck.lever@...cle.com,
jlayton@...nel.org, trondmy@...merspace.com, anna.schumaker@...cle.com,
hch@....de, sagi@...mberg.me, kch@...dia.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
linux-nfs@...r.kernel.org, linux-nvme@...ts.infradead.org,
netdev@...r.kernel.org, kernel-tls-handshake@...ts.linux.dev,
neil@...wn.name, Dai.Ngo@...cle.com, tom@...pey.com, horms@...nel.org
Subject: Re: [PATCH v2 3/4] nvmet-tcp: fix handling of tls alerts
On 9/15/25 17:45, Keith Busch wrote:
> On Fri, Sep 05, 2025 at 12:10:21PM -0400, Olga Kornievskaia wrote:
>> Dear NvME maintainers,
>>
>> Are there objections to this patch? What's the path forward to
>> including it in the nvme code.
>
> Sorry for the delay here. This series is mostly outside the nvme driver,
> so we need at least need an Ack from the networking folks if we're going
> to take this through the nvme tree.
>
I would opt for taking it through the networking tree. For NVMe it's
'just' a stub (ie erroring out on TLS alerts), so really we're not doing
much with the information.
Olga? Chuck?
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@...e.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
Powered by blists - more mailing lists