From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [v2 PATCH 2/3] crypto: padlock-sha - Use init_tfm/exit_tfm interface
Date: Tue, 10 Dec 2019 19:31:10 -0800 [thread overview]
Message-ID: <20191211033110.GE732@sol.localdomain> (raw)
In-Reply-To: <E1idpLI-0008Rc-L5@gondobar>
On Sun, Dec 08, 2019 at 01:42:52PM +0800, Herbert Xu wrote:
> @@ -231,6 +225,8 @@ static struct shash_alg sha1_alg = {
> .final = padlock_sha1_final,
> .export = padlock_sha_export,
> .import = padlock_sha_import,
> + .init_tfm = padlock_cra_init,
> + .exit_tfm = padlock_cra_exit,
> .descsize = sizeof(struct padlock_sha_desc),
> .statesize = sizeof(struct sha1_state),
Nit: these should be renamed to padlock_sha_init_tfm() and
padlock_sha_exit_tfm().
- Eric
next prev parent reply other threads:[~2019-12-11 3:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 2:35 [PATCH 0/3] crypto: shash - Enforce descsize limit in init_tfm Herbert Xu
2019-12-06 2:36 ` [PATCH 1/3] crypto: shash - Add init_tfm/exit_tfm and verify descsize Herbert Xu
2019-12-06 21:54 ` Eric Biggers
2019-12-06 2:36 ` [PATCH 2/3] crypto: padlock-sha - Use init_tfm/exit_tfm interface Herbert Xu
2019-12-06 2:36 ` [PATCH 3/3] crypto: hmac " Herbert Xu
2019-12-06 21:58 ` Eric Biggers
2019-12-08 5:42 ` [v2 PATCH 0/3] crypto: shash - Enforce descsize limit in init_tfm Herbert Xu
2019-12-08 5:42 ` [v2 PATCH 1/3] crypto: shash - Add init_tfm/exit_tfm and verify descsize Herbert Xu
2019-12-11 3:30 ` Eric Biggers
2019-12-08 5:42 ` [v2 PATCH 2/3] crypto: padlock-sha - Use init_tfm/exit_tfm interface Herbert Xu
2019-12-11 3:31 ` Eric Biggers [this message]
2019-12-08 5:42 ` [v2 PATCH 3/3] crypto: hmac " Herbert Xu
2019-12-11 3:32 ` [v2 PATCH 0/3] crypto: shash - Enforce descsize limit in init_tfm Eric Biggers
2019-12-11 8:30 ` 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=20191211033110.GE732@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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).