From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Dave Watson <davejwatson@fb.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Dave Miller <davem@davemloft.net>,
Vakul Garg <vakul.garg@nxp.com>,
Boris Pismenny <borisp@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
John Fastabend <john.fastabend@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH net-next 1/7] net: tls: Save iv in tls_rec for async crypto requests
Date: Thu, 24 Jan 2019 14:14:52 -0800 [thread overview]
Message-ID: <20190124141452.062d6d36@cakuba.netronome.com> (raw)
In-Reply-To: <20190124172146.q4acuud6z35wevm4@davejwatson-mba.dhcp.thefacebook.com>
On Thu, 24 Jan 2019 17:20:12 +0000, 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 async crypto manager (to test the async
> codepath), however I don't think this combination can happen in the wild.
> Presumably other hardware offloads will need this fix, but there have been
> no user reports.
>
> Fixes: a42055e8d2c30 ("Add support for async encryption of records...")
> Signed-off-by: Dave Watson <davejwatson@fb.com>
This one should target net, no?
next prev parent reply other threads:[~2019-01-24 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 17:20 [PATCH net-next 1/7] net: tls: Save iv in tls_rec for async crypto requests Dave Watson
2019-01-24 22:14 ` Jakub Kicinski [this message]
2019-01-24 22:34 ` Dave Watson
2019-01-25 1:23 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190124141452.062d6d36@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vakul.garg@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox