From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: Hongbo Li <herbert.tencent@gmail.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
herbert@gondor.apana.org.au, ebiggers@kernel.org,
dhowells@redhat.com, jarkko@kernel.org, herberthbli@tencent.com
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] crypto: sm2 - fix a memory leak in sm2
Date: Tue, 1 Jun 2021 10:54:07 +0800 [thread overview]
Message-ID: <91999e12-a7de-ad4b-72c4-2376ac682c92@linux.alibaba.com> (raw)
In-Reply-To: <1622467801-30957-1-git-send-email-herbert.tencent@gmail.com>
Hi Hongbo,
On 5/31/21 9:30 PM, Hongbo Li wrote:
> From: Hongbo Li <herberthbli@tencent.com>
>
> SM2 module alloc ec->Q in sm2_set_pub_key(), when doing alg test in
> test_akcipher_one(), it will set public key for every test vector,
> and don't free ec->Q. This will cause a memory leak.
>
> This patch alloc ec->Q in sm2_ec_ctx_init().
>
> Fixes: ea7ecb66440b ("crypto: sm2 - introduce OSCCA SM2 asymmetric cipher algorithm")
> Signed-off-by: Hongbo Li <herberthbli@tencent.com>
> Reviewed-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
> ---
> crypto/sm2.c | 24 ++++++++++--------------
> 1 file changed, 10 insertions(+), 14 deletions(-)
>
Just add Cc: to SOB, like this:
Fixes: ea7ecb66440b (...)
Signed-off-by: Hongbo Li <herberthbli@tencent.com>
Cc: stable@vger.kernel.org # v5.10+
Reviewed-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
Thanks,
Tianjia
next prev parent reply other threads:[~2021-06-01 2:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 13:30 [PATCH] crypto: sm2 - fix a memory leak in sm2 Hongbo Li
2021-05-31 14:09 ` Greg KH
2021-06-01 2:54 ` Tianjia Zhang [this message]
2021-06-01 13:04 ` hongbo li
[not found] <1622552752-15501-1-git-send-email-herbert.tencent@gmail.com>
2021-06-03 12:34 ` Herbert Xu
2021-06-04 2:11 ` hongbo li
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=91999e12-a7de-ad4b-72c4-2376ac682c92@linux.alibaba.com \
--to=tianjia.zhang@linux.alibaba.com \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=herbert.tencent@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=herberthbli@tencent.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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