From: Herbert Xu <herbert@gondor.apana.org.au>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: dan.carpenter@oracle.com, davem@davemloft.net,
jernej.skrabec@siol.net, mripard@kernel.org, wens@csie.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] crypto: sun8i-ss: fix result memory leak on error path
Date: Fri, 12 Mar 2021 20:31:40 +1100 [thread overview]
Message-ID: <20210312093139.GA728@gondor.apana.org.au> (raw)
In-Reply-To: <20210302164145.28552-1-clabbe.montjoie@gmail.com>
On Tue, Mar 02, 2021 at 05:41:45PM +0100, Corentin Labbe wrote:
> This patch fixes a memory leak on an error path.
>
> Fixes: d9b45418a917 ("crypto: sun8i-ss - support hash algorithms")
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
> ---
> drivers/crypto/allwinner/sun8i-ss/sun8i-ss-hash.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This patch was already merged a month ago:
commit 1dbc6a1e25be8575d6c4114d1d2b841a796507f7
Author: Corentin Labbe <clabbe.montjoie@gmail.com>
Date: Fri Feb 12 09:46:10 2021 +0100
crypto: sun8i-ss - fix result memory leak on error path
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2021-03-12 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 16:41 [PATCH] crypto: sun8i-ss: fix result memory leak on error path Corentin Labbe
2021-03-12 9:31 ` Herbert Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-12 8:46 Corentin Labbe
2021-03-04 6:44 ` 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=20210312093139.GA728@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=clabbe.montjoie@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=lkp@intel.com \
--cc=mripard@kernel.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).