From: Herbert Xu <herbert@gondor.apana.org.au>
To: Vakul Garg <vakul@freescale.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH][RESEND] crypto: caam - Fixed the memory out of bound overwrite issue
Date: Wed, 10 Jul 2013 16:52:05 +1000 [thread overview]
Message-ID: <20130710065205.GA32296@gondor.apana.org.au> (raw)
In-Reply-To: <1373437573-21588-1-git-send-email-vakul@freescale.com>
On Wed, Jul 10, 2013 at 06:26:13AM +0000, Vakul Garg wrote:
> When kernel is compiled with CONFIG_SLUB_DEBUG=y and
> CRYPTO_MANAGER_DISABLE_TESTS=n, during kernel bootup, the kernel
> reports error given below. The root cause is that in function
> hash_digest_key(), for allocating descriptor, insufficient memory was
> being allocated. The required number of descriptor words apart from
> input and output pointers are 8 (instead of 6).
Patch applied to crypto. 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
prev parent reply other threads:[~2013-07-10 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 6:26 [PATCH][RESEND] crypto: caam - Fixed the memory out of bound overwrite issue Vakul Garg
2013-07-10 6:52 ` Herbert Xu [this message]
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=20130710065205.GA32296@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=vakul@freescale.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