[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a17850bb-f70d-1f77-3823-afd70816ce57@huawei.com>
Date: Mon, 25 May 2020 15:13:24 +0800
From: "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)"
<longpeng2@...wei.com>
To: Markus Elfring <Markus.Elfring@....de>,
<linux-crypto@...r.kernel.org>,
<virtualization@...ts.linux-foundation.org>
CC: Arei Gonglei <arei.gonglei@...wei.com>,
Corentin Labbe <clabbe@...libre.com>,
"David S. Miller" <davem@...emloft.net>,
Herbert Xu <herbert@...dor.apana.org.au>,
Jason Wang <jasowang@...hat.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] crypto: virtio: Fix use-after-free in
virtio_crypto_skcipher_finalize_req()
Hi Markus,
On 2020/5/25 14:30, Markus Elfring wrote:
>> … So the system will crash
>> at last when this memory be used again.
>
> I would prefer a wording with less typos here.
>
Could you help me to make the sentence better?
>
>> We can free the resources before calling ->complete to fix this issue.
>
> * An imperative wording can be nicer.
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=9cb1fd0efd195590b828b9b865421ad345a4a145#n151
>
I'll try.
> * You proposed to move a call of the function “crypto_finalize_skcipher_request”.
> How does this change fit to the mentioned position?
>
The resources which need to be freed is not used anymore, but the pointers
of these resources may be changed in the function
"crypto_finalize_skcipher_request", so free these resources before call the
function is suitable.
> * Would you like to add the tag “Fixes” to the commit message?
>
OK.
> Regards,
> Markus
>
--
---
Regards,
Longpeng(Mike)
Powered by blists - more mailing lists