[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190303.221141.1436721157357099541.davem@davemloft.net>
Date: Sun, 03 Mar 2019 22:11:41 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: borisp@...lanox.com
Cc: aviadye@...lanox.com, davejwatson@...com, john.fastabend@...il.com,
daniel@...earbox.net, vakul.garg@....com, netdev@...r.kernel.org,
eranbe@...lanox.com
Subject: Re: [PATCH v2 net 0/4] tls: Fix issues in tls_device
From: Boris Pismenny <borisp@...lanox.com>
Date: Sat, 2 Mar 2019 17:05:59 +0000
>
> 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.
Thanks for the clarification, series applied, thanks.
Powered by blists - more mailing lists