netdev - Re: [PATCH 07/17] net/tls: handle MSG_EOR for tls

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 10 May 2023 02:02:39 +0300
From: Max Gurtovoy <mgurtovoy@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>, Hannes Reinecke <hare@...e.de>
Cc: Sagi Grimberg <sagi@...mberg.me>, Christoph Hellwig <hch@....de>,
 Keith Busch <kbusch@...nel.org>, linux-nvme@...ts.infradead.org,
 Chuck Lever <chuck.lever@...cle.com>, kernel-tls-handshake@...ts.linux.dev,
 "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH 07/17] net/tls: handle MSG_EOR for tls_sw TX flow



On 09/05/2023 18:13, Jakub Kicinski wrote:
> On Tue, 9 May 2023 16:18:30 +0200 Hannes Reinecke wrote:
>>> This seems like a nice optimization but seems not mandatory for the
>>> acceptance of TLS support in nvme/tcp.
>>>
>>> I wonder if this can go to net/tls as a standalone patch ?
>>
>> Errm. Without this NVMe/TLS will not work as sendmsg/sendpage will
>> bail out.
>> So yes, surely it can be applied as a standalone patch, but that
>> only makes sense if it will be applied _before_ the rest of the
>> nvme/tls patches.

how come it will bail out only for NVMe/TLS and not for Other_user/TLS ?

>>
>> Not sure how best to coordinate this.
> 
> You should apply it on a branch based on -rc1 and then both us and
> $appropriate-nvme-maintainer can pull it in.