linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Horia Geanta <horia.geanta@freescale.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH crypto 1/2] crypto: caam - fix mem leak in ahash_setkey
Date: Wed, 23 Apr 2014 01:47:32 +0200	[thread overview]
Message-ID: <201404230147.32552.marex@denx.de> (raw)
In-Reply-To: <1397815302-15915-1-git-send-email-horia.geanta@freescale.com>

On Friday, April 18, 2014 at 12:01:41 PM, Horia Geanta wrote:
> In case hash key is bigger than algorithm block size, it is hashed.
> In this case, memory is allocated to keep this hash in hashed_key.
> hashed_key has to be freed on the key_dma dma mapping error path.
> 
> Cc: <stable@vger.kernel.org> # 3.10+
> Signed-off-by: Horia Geanta <horia.geanta@freescale.com>
> ---
>  drivers/crypto/caam/caamhash.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/crypto/caam/caamhash.c
> b/drivers/crypto/caam/caamhash.c index 0378328f47a7..2d244e629ed2 100644
> --- a/drivers/crypto/caam/caamhash.c
> +++ b/drivers/crypto/caam/caamhash.c
> @@ -545,7 +545,8 @@ static int ahash_setkey(struct crypto_ahash *ahash,
>  				      DMA_TO_DEVICE);
>  	if (dma_mapping_error(jrdev, ctx->key_dma)) {
>  		dev_err(jrdev, "unable to map key i/o memory\n");
> -		return -ENOMEM;
> +		ret = -ENOMEM;
> +		goto map_err;
>  	}
>  #ifdef DEBUG
>  	print_hex_dump(KERN_ERR, "ctx.key@"__stringify(__LINE__)": ",
> @@ -559,6 +560,7 @@ static int ahash_setkey(struct crypto_ahash *ahash,
>  				 DMA_TO_DEVICE);
>  	}
> 
> +map_err:
>  	kfree(hashed_key);

Reviewed-by: Marek Vasut <marex@denx.de>

btw you might want to clean up the use of printk() vs. dev_*() throughout the 
driver, it's horribly intermixed. It'd be nice to use just dev_*() for output.
Stuff like
#ifdef DEBUG
printk(...)
#endif
can be easily replaced with dev_dbg() for example ...

Best regards,
Marek Vasut

  parent reply	other threads:[~2014-04-22 23:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 10:01 [PATCH crypto 1/2] crypto: caam - fix mem leak in ahash_setkey Horia Geanta
2014-04-18 10:01 ` [PATCH crypto 2/2] crypto: caam - add allocation failure handling in SPRINTFCAT macro Horia Geanta
2014-04-22 23:56   ` Marek Vasut
2014-04-23 16:35     ` Horia Geantă
2014-04-23 17:12       ` Marek Vasut
2014-04-23 17:41         ` Marek Vasut
2014-04-28 10:24   ` Herbert Xu
2014-04-28 19:28     ` Marek Vasut
2014-04-28 21:53       ` Herbert Xu
2014-04-28 22:29         ` Marek Vasut
2014-04-22 23:47 ` Marek Vasut [this message]
2014-04-28 10:25   ` [PATCH crypto 1/2] crypto: caam - fix mem leak in ahash_setkey 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=201404230147.32552.marex@denx.de \
    --to=marex@denx.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@freescale.com \
    --cc=linux-crypto@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;
as well as URLs for NNTP newsgroup(s).