From: "Horia Geantă" <horia.geanta@nxp.com>
To: Iuliana Prodan <iuliana.prodan@nxp.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Aymen Sghaier <aymen.sghaier@nxp.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Silvano Di Ninno <silvano.dininno@nxp.com>,
Franck Lenormand <franck.lenormand@nxp.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v2 0/4] crypto: caam - fix use-after-free KASAN issue
Date: Tue, 7 Apr 2020 10:39:33 +0300 [thread overview]
Message-ID: <a0715aa8-e19e-1a1d-a924-e8a2d3f076fa@nxp.com> (raw)
In-Reply-To: <1586213248-4230-1-git-send-email-iuliana.prodan@nxp.com>
On 4/7/2020 1:47 AM, Iuliana Prodan wrote:
> This series fixes a use-after-free KASAN issue that was introduce
> by CAAM backlogging support[1].
> This is fixed for SKCIPHER, HASH, RSA and AEAD algorithms.
>
> [1] https://patchwork.kernel.org/cover/11378941/
>
For the series:
Reviewed-by: Horia Geantă <horia.geanta@nxp.com>
though the Cc: stable should be removed, since the commits being fixed
will only show up in v5.7-rc1.
Herbert, could you do this when merging or you prefer instead v3?
Thanks,
Horia
next prev parent reply other threads:[~2020-04-07 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 22:47 [PATCH v2 0/4] crypto: caam - fix use-after-free KASAN issue Iuliana Prodan
2020-04-06 22:47 ` [PATCH v2 1/4] crypto: caam - fix use-after-free KASAN issue for SKCIPHER algorithms Iuliana Prodan
2020-04-06 22:47 ` [PATCH v2 2/4] crypto: caam - fix use-after-free KASAN issue for AEAD algorithms Iuliana Prodan
2020-04-06 22:47 ` [PATCH v2 3/4] crypto: caam - fix use-after-free KASAN issue for HASH algorithms Iuliana Prodan
2020-04-06 22:47 ` [PATCH v2 4/4] crypto: caam - fix use-after-free KASAN issue for RSA algorithms Iuliana Prodan
2020-04-07 7:39 ` Horia Geantă [this message]
2020-04-16 6:50 ` [PATCH v2 0/4] crypto: caam - fix use-after-free KASAN issue Herbert Xu
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=a0715aa8-e19e-1a1d-a924-e8a2d3f076fa@nxp.com \
--to=horia.geanta@nxp.com \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=franck.lenormand@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=iuliana.prodan@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=silvano.dininno@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;
as well as URLs for NNTP newsgroup(s).