[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ae2f2ff2-dc9a-5cf0-6614-63d4fcff59d8@mellanox.com>
Date: Sat, 2 Mar 2019 17:05:59 +0000
From: Boris Pismenny <borisp@...lanox.com>
To: David Miller <davem@...emloft.net>
CC: Aviad Yehezkel <aviadye@...lanox.com>,
"davejwatson@...com" <davejwatson@...com>,
"john.fastabend@...il.com" <john.fastabend@...il.com>,
"daniel@...earbox.net" <daniel@...earbox.net>,
"vakul.garg@....com" <vakul.garg@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Eran Ben Elisha <eranbe@...lanox.com>
Subject: Re: [PATCH v2 net 0/4] tls: Fix issues in tls_device
On 03/02/19 02:52, David Miller wrote:
> From: Boris Pismenny <borisp@...lanox.com>
> Date: Wed, 27 Feb 2019 17:38:02 +0200
>
>> This series fixes issues encountered in tls_device code paths,
>> which were introduced recently.
>>
>> Additionally, this series includes a fix for tls software only receive flow,
>> which causes corruption of payload received by user space applications.
>>
>> This series was tested using the OpenSSL integration of KTLS -
>> https://github.com/mellan
> This series doesn't apply cleanly to net any longer, please respin.
>
> Thank you.
Sorry for the confusion. I meant net-next. Thanks.
Powered by blists - more mailing lists