[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <df8a9c03-de99-4d2f-e577-05924002136e@huawei.com>
Date: Mon, 19 Apr 2021 19:50:17 +0800
From: Hui Tang <tanghui20@...wei.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
CC: <davem@...emloft.net>, <linux-crypto@...r.kernel.org>,
<xuzaibo@...wei.com>, <wangzhou1@...ilicon.com>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] crypto: hisilicon/hpre - fix unmapping invalid dma
address
On 2021/4/16 19:26, Herbert Xu wrote:
> On Sat, Apr 10, 2021 at 05:49:17PM +0800, Hui Tang wrote:
>> Currently, an invalid dma address may be unmapped when calling
>> 'xx_data_clr_all' in error path, so check dma address of sqe in/out
>> whether it has been mapped before calling 'dma_free_coherent' or
>> 'dma_unmap_single'.
>>
>> An abnormal case is as follows:
>> hpre_curve25519_compute_value
>> -> hpre_curve25519_src_init
>> -> hpre_curve25519_hw_data_clr_all
>>
>> Fixes: a9214b0b6ed2(crypto: hisilicon - fix the check on dma address)
>> Signed-off-by: Hui Tang <tanghui20@...wei.com>
>> ---
>> drivers/crypto/hisilicon/hpre/hpre_crypto.c | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>
> This triggers new sparse warnings.
Thanks, I will fix it in 5.13 rc1.
Powered by blists - more mailing lists