From: Li Huafei <lihuafei1@huawei.com>
To: Antoine Tenart <atenart@kernel.org>, <davem@davemloft.net>,
<herbert@gondor.apana.org.au>, <pliem@maxlinear.com>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: inside-secure - Fix the return value of safexcel_xcbcmac_cra_init()
Date: Thu, 7 Nov 2024 09:18:33 +0800 [thread overview]
Message-ID: <b4fd8b58-1736-d2ef-0c81-6cb97a7987d4@huawei.com> (raw)
In-Reply-To: <173082242323.5505.14169181853894683603@kwain>
On 2024/11/6 0:00, Antoine Tenart wrote:
> Quoting Li Huafei (2024-10-31 12:27:55)
>> The commit 320406cb60b6 ("crypto: inside-secure - Replace generic aes
>> with libaes") replaced crypto_alloc_cipher() with kmalloc(), but did not
>> modify the handling of the return value. When kmalloc() returns NULL,
>> PTR_ERR_OR_ZERO(NULL) returns 0, but in fact, the memory allocation has
>> failed, and -ENOMEM should be returned.
>>
>> Fixes: 320406cb60b6 ("crypto: inside-secure - Replace generic aes with libaes")
>> Signed-off-by: Li Huafei <lihuafei1@huawei.com>
>
> Acked-by: Antoine Tenart <atenart@kernel.org>
>
> Thanks!
>
Thank you for reviewing.
>> ---
>> drivers/crypto/inside-secure/safexcel_hash.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/crypto/inside-secure/safexcel_hash.c b/drivers/crypto/inside-secure/safexcel_hash.c
>> index e17577b785c3..f44c08f5f5ec 100644
>> --- a/drivers/crypto/inside-secure/safexcel_hash.c
>> +++ b/drivers/crypto/inside-secure/safexcel_hash.c
>> @@ -2093,7 +2093,7 @@ static int safexcel_xcbcmac_cra_init(struct crypto_tfm *tfm)
>>
>> safexcel_ahash_cra_init(tfm);
>> ctx->aes = kmalloc(sizeof(*ctx->aes), GFP_KERNEL);
>> - return PTR_ERR_OR_ZERO(ctx->aes);
>> + return ctx->aes == NULL ? -ENOMEM : 0;
>> }
>>
>> static void safexcel_xcbcmac_cra_exit(struct crypto_tfm *tfm)
>> --
>> 2.25.1
>>
> .
>
next prev parent reply other threads:[~2024-11-07 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 11:27 Li Huafei
2024-11-05 16:00 ` Antoine Tenart
2024-11-07 1:18 ` Li Huafei [this message]
2024-11-10 3:55 ` 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=b4fd8b58-1736-d2ef-0c81-6cb97a7987d4@huawei.com \
--to=lihuafei1@huawei.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pliem@maxlinear.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
all inboxes | Powered by JetHome®