From: Dave Watson
Date: Thu, 24 Jan 2019 22:34:29 +
> Later patches touch the same code, so would need to be in both to
> avoid merge conflicts.
Dave, here is the way you should handle this.
Submit this patch for net. Let me know that something you want to
submit for net-next depends upon
On 01/24/19 02:14 PM, Jakub Kicinski wrote:
> On Thu, 24 Jan 2019 17:20:12 +, Dave Watson wrote:
> > aead_request_set_crypt takes an iv pointer, and we change the iv
> > soon after setting it. Some async crypto algorithms don't save the iv,
> > so we need to save it in the tls_rec for async re
On Thu, 24 Jan 2019 17:20:12 +, Dave Watson wrote:
> aead_request_set_crypt takes an iv pointer, and we change the iv
> soon after setting it. Some async crypto algorithms don't save the iv,
> so we need to save it in the tls_rec for async requests.
>
> Found by hardcoding x64 aesni to use as
aead_request_set_crypt takes an iv pointer, and we change the iv
soon after setting it. Some async crypto algorithms don't save the iv,
so we need to save it in the tls_rec for async requests.
Found by hardcoding x64 aesni to use async crypto manager (to test the async
codepath), however I don't
