From: Sebastian Andrzej Siewior <linux-crypto@ml.breakpoint.cc>
To: Huang Ying <ying.huang@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [RFC 2/7] crypto: Use GHASH digest algorithm in GCM
Date: Wed, 17 Jun 2009 22:47:36 +0200 [thread overview]
Message-ID: <20090617204736.GC28694@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <1244704228.5320.125.camel@yhuang-dev.sh.intel.com>
* Huang Ying | 2009-06-11 15:10:28 [+0800]:
>Remove the dedicated GHASH implementation in GCM, and uses the GHASH
>digest algorithm instead. This will make GCM uses hardware accelerated
>GHASH implementation automatically if available.
>
>ahash instead of shash interface is used, because some hardware
>accelerated GHASH implementation needs asynchronous interface.
The outside interface is also async so this should work.
>Signed-off-by: Huang Ying <ying.huang@intel.com>
>
>@@ -796,14 +996,15 @@ static int __init crypto_gcm_module_init
> if (err)
> goto out_undo_gcm;
>
>-out:
>- return err;
>+ return 0;
>
> out_undo_gcm:
> crypto_unregister_template(&crypto_gcm_tmpl);
> out_undo_base:
> crypto_unregister_template(&crypto_gcm_base_tmpl);
>- goto out;
>+out:
>+ kfree(gcm_zeroes);
>+ return err;
> }
>
> static void __exit crypto_gcm_module_exit(void)
here you are leaking gcm_zeroes
Sebastian
next prev parent reply other threads:[~2009-06-17 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 7:10 Huang Ying
2009-06-17 20:47 ` Sebastian Andrzej Siewior [this message]
2009-06-18 2:09 ` Huang Ying
2009-06-21 13:46 ` Herbert Xu
2009-06-22 1:41 ` Huang Ying
2009-06-22 2:03 ` Herbert Xu
2009-06-22 2:07 ` Huang Ying
2009-06-22 2:19 ` 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=20090617204736.GC28694@Chamillionaire.breakpoint.cc \
--to=linux-crypto@ml.breakpoint.cc \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@intel.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®