From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sasha Levin <sashal@kernel.org>
Cc: "Longpeng(Mike)" <longpeng2@huawei.com>,
linux-crypto@vger.kernel.org, Gonglei <arei.gonglei@huawei.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jason Wang <jasowang@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Markus Elfring <Markus.Elfring@web.de>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req()
Date: Sun, 31 May 2020 05:21:48 -0400 [thread overview]
Message-ID: <20200531052126-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200526141138.8410D207FB@mail.kernel.org>
On Tue, May 26, 2020 at 02:11:37PM +0000, Sasha Levin wrote:
> <20200123101000.GB24255@Red>
> References: <20200526031956.1897-3-longpeng2@huawei.com>
> <20200123101000.GB24255@Red>
>
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag
> fixing commit: dbaf0624ffa5 ("crypto: add virtio-crypto driver").
>
> The bot has tested the following trees: v5.6.14, v5.4.42, v4.19.124, v4.14.181.
>
> v5.6.14: Build OK!
> v5.4.42: Failed to apply! Possible dependencies:
> eee1d6fca0a0 ("crypto: virtio - switch to skcipher API")
>
> v4.19.124: Failed to apply! Possible dependencies:
> eee1d6fca0a0 ("crypto: virtio - switch to skcipher API")
>
> v4.14.181: Failed to apply! Possible dependencies:
> 500e6807ce93 ("crypto: virtio - implement missing support for output IVs")
> 67189375bb3a ("crypto: virtio - convert to new crypto engine API")
> d0d859bb87ac ("crypto: virtio - Register an algo only if it's supported")
> e02b8b43f55a ("crypto: virtio - pr_err() strings should end with newlines")
> eee1d6fca0a0 ("crypto: virtio - switch to skcipher API")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
Mike could you comment on backporting?
> --
> Thanks
> Sasha
next prev parent reply other threads:[~2020-05-31 9:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 3:19 [PATCH v2 0/2] crypto: virtio: Fix two crash issue Longpeng(Mike)
2020-05-26 3:19 ` [PATCH v2 1/2] crypto: virtio: Fix src/dst scatterlist calculation in __virtio_crypto_skcipher_do_req() Longpeng(Mike)
2020-05-26 7:03 ` Markus Elfring
2020-05-26 7:21 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-05-26 8:25 ` [v2 " Markus Elfring
2020-05-26 14:11 ` [PATCH v2 " Sasha Levin
2020-05-26 14:11 ` Sasha Levin
2020-05-26 3:19 ` [PATCH v2 2/2] crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req() Longpeng(Mike)
2020-05-26 7:19 ` Markus Elfring
2020-05-26 7:38 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-05-26 9:01 ` [v2 " Markus Elfring
2020-05-26 9:24 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-05-26 9:30 ` Markus Elfring
2020-05-26 10:16 ` Greg KH
2020-05-26 12:00 ` [PATCH v2 " Gonglei (Arei)
2020-05-26 14:11 ` Sasha Levin
2020-05-31 9:21 ` Michael S. Tsirkin [this message]
2020-06-02 3:54 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-05-26 14:11 ` Sasha Levin
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=20200531052126-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Markus.Elfring@web.de \
--cc=arei.gonglei@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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).