[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230207105036.76b30090@kernel.org>
Date: Tue, 7 Feb 2023 10:50:36 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Alasdair Kergon <agk@...hat.com>,
Mike Snitzer <snitzer@...nel.org>, dm-devel@...hat.com,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
Tyler Hicks <code@...icks.com>, ecryptfs@...r.kernel.org,
Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>,
linux-bluetooth@...r.kernel.org,
Steffen Klassert <steffen.klassert@...unet.com>,
Jon Maloy <jmaloy@...hat.com>,
Ying Xue <ying.xue@...driver.com>,
Boris Pismenny <borisp@...dia.com>,
John Fastabend <john.fastabend@...il.com>,
David Howells <dhowells@...hat.com>,
Jarkko Sakkinen <jarkko@...nel.org>, keyrings@...r.kernel.org
Subject: Re: [PATCH] tls: Pass rec instead of aead_req into tls_encrypt_done
On Tue, 7 Feb 2023 16:18:36 +0800 Herbert Xu wrote:
> > > aead_request_set_callback(aead_req, CRYPTO_TFM_REQ_MAY_BACKLOG,
> > > - tls_encrypt_done, sk);
> > > + tls_encrypt_done, aead_req);
> >
> > ... let's just pass rec instead of aead_req here, then?
>
> Good point. Could we do this as a follow-up patch? Reposting
> the whole series would disturb a lot of people. Of course if
> other major issues crop up I can fold this into the existing
> patch.
Whatever works best!
Reviewed-by: Jakub Kicinski <kuba@...nel.org>
Powered by blists - more mailing lists