From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: mathew.j.martineau@linux.intel.com, dhowells@redhat.com,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 1/4] crypto: add template handling for RNGs
Date: Mon, 18 Jul 2016 09:18:18 +0200 [thread overview]
Message-ID: <1484377.C9YnUIxR2D@tauon.atsec.com> (raw)
In-Reply-To: <20160718071417.GA12600@gondor.apana.org.au>
Am Montag, 18. Juli 2016, 15:14:17 schrieb Herbert Xu:
Hi Herbert,
> >
> > diff --git a/crypto/rng.c b/crypto/rng.c
> > index b81cffb..92cc02a 100644
> > --- a/crypto/rng.c
> > +++ b/crypto/rng.c
> > @@ -232,5 +232,36 @@ void crypto_unregister_rngs(struct rng_alg *algs, int
> > count) }
> > EXPORT_SYMBOL_GPL(crypto_unregister_rngs);
> >
> > +void rng_free_instance(struct crypto_instance *inst)
> > +{
> > + crypto_drop_spawn(crypto_instance_ctx(inst));
> > + kfree(rng_instance(inst));
> > +}
>
> Please use the new free interface, i.e.,
>
> void rng_free_instance(struct rng_instance *inst)
>
> and then
>
> inst->free = rng_free_instance;
>
> > +static inline struct rng_alg *__crypto_rng_alg(struct crypto_alg *alg)
> > +{
> > + return container_of(alg, struct rng_alg, base);
> > +}
> > +
> > +static inline struct rng_instance *rng_instance(
> > + struct crypto_instance *inst)
> > +{
> > + return container_of(__crypto_rng_alg(&inst->alg),
> > + struct rng_instance, alg);
> > +}
>
> These two can then be deleted.
Thanks. I will add that to the next round.
>
> Thanks,
Ciao
Stephan
next prev parent reply other threads:[~2016-07-18 7:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 9:06 [RFC PATCH] KEYS: add SP800-56A KDF support for DH Stephan Mueller
2016-07-12 9:06 ` [PATCH v3 0/4] crypto: Key Derivation Function (SP800-108) Stephan Mueller
2016-07-12 9:07 ` [PATCH v3 1/4] crypto: add template handling for RNGs Stephan Mueller
2016-07-18 7:14 ` Herbert Xu
2016-07-18 7:18 ` Stephan Mueller [this message]
2016-07-18 15:23 ` Sandy Harris
2016-07-18 15:37 ` Stephan Mueller
2016-07-12 9:07 ` [PATCH v3 2/4] crypto: kdf - add known answer tests Stephan Mueller
2016-07-12 9:07 ` [PATCH v3 3/4] crypto: kdf - SP800-108 Key Derivation Function Stephan Mueller
2016-07-12 9:08 ` [PATCH v3 4/4] crypto: kdf - enable compilation Stephan Mueller
2016-07-12 9:08 ` [PATCH] DH support: add KDF handling support Stephan Mueller
2016-07-13 23:17 ` Mat Martineau
2016-07-14 6:54 ` Stephan Mueller
2016-07-14 8:00 ` Jeffrey Walton
2016-07-14 14:19 ` Stephan Mueller
2016-07-14 23:47 ` Mat Martineau
2016-07-27 7:55 ` David Howells
2016-07-27 9:11 ` Stephan Mueller
2016-07-15 0:45 ` [RFC PATCH] KEYS: add SP800-56A KDF support for DH Mat Martineau
2016-07-15 16:38 ` Stephan Mueller
2016-07-15 18:45 ` Mat Martineau
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=1484377.C9YnUIxR2D@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mathew.j.martineau@linux.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;
as well as URLs for NNTP newsgroup(s).