From: Sasha Levin <sashal@kernel.org> To: Sasha Levin <sashal@kernel.org> To: "Longpeng(Mike)" <longpeng2@huawei.com> To: <linux-crypto@vger.kernel.org> Cc: "Longpeng(Mike)" <longpeng2@huawei.com> Cc: Gonglei <arei.gonglei@huawei.com> Cc: Herbert Xu <herbert@gondor.apana.org.au> Cc: "Michael S. Tsirkin" <mst@redhat.com> Cc: Jason Wang <jasowang@redhat.com> Cc: "David S. Miller" <davem@davemloft.net> Cc: virtualization@lists.linux-foundation.org Cc: linux-kernel@vger.kernel.org Cc: stable@vger.kernel.org Cc: stable@vger.kernel.org Subject: Re: [PATCH v3 2/3] crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req() Date: Fri, 05 Jun 2020 14:10:51 +0000 [thread overview] Message-ID: <20200605141051.BAE3D207D8@mail.kernel.org> (raw) In-Reply-To: <20200602070501.2023-3-longpeng2@huawei.com> <20200123101000.GB24255@Red> References: <20200602070501.2023-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.15, v5.4.43, v4.19.125, v4.14.182. v5.6.15: Build OK! v5.4.43: Failed to apply! Possible dependencies: eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") v4.19.125: Failed to apply! Possible dependencies: eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") v4.14.182: 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? -- Thanks Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org> To: Sasha Levin <sashal@kernel.org>, linux-crypto@vger.kernel.org Cc: "Longpeng(Mike)" <longpeng2@huawei.com>, Gonglei <arei.gonglei@huawei.com>, Herbert Xu <herbert@gondor.apana.org.au>, "Michael S. Tsirkin" <mst@redhat.com>, Jason Wang <jasowang@redhat.com>, "David S. Miller" <davem@davemloft.net>, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, stable@vger.kernel.orgstable@vger.kernel.org Subject: Re: [PATCH v3 2/3] crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req() Date: Fri, 05 Jun 2020 14:10:51 +0000 [thread overview] Message-ID: <20200605141051.BAE3D207D8@mail.kernel.org> (raw) In-Reply-To: <20200602070501.2023-3-longpeng2@huawei.com> <20200123101000.GB24255@Red> References: <20200602070501.2023-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.15, v5.4.43, v4.19.125, v4.14.182. v5.6.15: Build OK! v5.4.43: Failed to apply! Possible dependencies: eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") v4.19.125: Failed to apply! Possible dependencies: eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") v4.14.182: 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? -- Thanks Sasha
next prev parent reply other threads:[~2020-06-05 14:10 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-02 7:04 [PATCH v3 0/3] crypto: virtio: Fix three issues Longpeng(Mike) 2020-06-02 7:04 ` Longpeng(Mike) 2020-06-02 7:04 ` [PATCH v3 1/3] crypto: virtio: Fix src/dst scatterlist calculation in __virtio_crypto_skcipher_do_req() Longpeng(Mike) 2020-06-02 7:04 ` Longpeng(Mike) 2020-06-05 14:10 ` Sasha Levin 2020-06-05 14:10 ` Sasha Levin 2020-06-10 7:38 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.) 2020-06-10 7:38 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.) 2020-06-05 14:10 ` Sasha Levin 2020-06-05 14:10 ` Sasha Levin 2020-06-02 7:05 ` [PATCH v3 2/3] crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req() Longpeng(Mike) 2020-06-02 7:05 ` Longpeng(Mike) 2020-06-05 14:10 ` Sasha Levin 2020-06-05 14:10 ` Sasha Levin [this message] 2020-06-05 14:10 ` Sasha Levin 2020-06-02 7:05 ` [PATCH v3 3/3] crypto: virtio: Fix dest length calculation in __virtio_crypto_skcipher_do_req() Longpeng(Mike) 2020-06-02 7:05 ` Longpeng(Mike) 2020-06-05 14:10 ` Sasha Levin 2020-06-05 14:10 ` Sasha Levin 2020-06-05 14:10 ` Sasha Levin 2020-06-05 14:10 ` 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=20200605141051.BAE3D207D8@mail.kernel.org \ --to=sashal@kernel.org \ --cc=longpeng2@huawei.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.