From: Joe Perches <joe@perches.com>
To: Stephan Mueller <smueller@chronox.de>,
herbert@gondor.apana.org.au, Theodore Tso <tytso@mit.edu>
Cc: sandyinchina@gmail.com, Jason Cooper <jason@lakedaemon.net>,
John Denker <jsd@av8n.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/6] crypto: Linux Random Number Generator
Date: Sun, 24 Apr 2016 04:30:24 -0700 [thread overview]
Message-ID: <1461497424.2726.55.camel@perches.com> (raw)
In-Reply-To: <4513249.IuhZztB3y6@positron.chronox.de>
On Sun, 2016-04-24 at 12:40 +0200, Stephan Mueller wrote:
> The LRNG with all its properties is documented in [1]. This
> documentation covers the functional discussion as well as testing of all
> aspects of entropy processing. In addition, the documentation explains
> the conducted regression tests to verify that the LRNG is API and ABI
> compatible with the legacy /dev/random implementation.
>
> [1] http://www.chronox.de/lrng.html
Thanks.
Links get stale.
It may be better to put an ascii version of the pdf
in Documentation/ and the test code in tools/
and some trivial notes:
> diff --git a/crypto/lrng.c b/crypto/lrng.c
[]
> +/* debug macro */
> +#define DRIVER_NAME "lrng"
Using
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
before any #include would be a lot more common.
> +#if 0
> +#define dbg(fmt, ...) pr_info(DRIVER_NAME": " fmt, ##__VA_ARGS__)
> +#else
> +#define dbg(fmt, ...)
> +#endif
pr_debug or is there some interaction with
dynamic_debug you want to avoid?
And it's generally better to use something like
#if 0
#define dbg(fmt, ...) pr_info(fmt, ##__VA_ARGS__)
#else
#define dbg(fmt, ...) no_printk(fmt, ##__VA_ARGS__)
so that new dbg statements would not have
format/argument mismatches and argument
evaluation side-effects are still eliminated.
> +static void lrng_pdrbg_init_ops(u32 entropy_bits)
> +{
> + if (lrng_pdrbg.pdrbg_fully_seeded)
> + return;
> +
> + BUILD_BUG_ON(LRNG_IRQ_MIN_NUM % LRNG_POOL_WORD_BITS);
> + BUILD_BUG_ON((LRNG_MIN_SEED_ENTROPY_BITS * LRNG_IRQ_ENTROPY_BITS /
> + LRNG_DRBG_SECURITY_STRENGTH_BITS) > LRNG_IRQ_MIN_NUM);
> +
> + /* DRBG is seeded with full security strength */
> + if (entropy_bits >= LRNG_DRBG_SECURITY_STRENGTH_BITS) {
> + lrng_pdrbg.pdrbg_fully_seeded = true;
> + lrng_pdrbg.pdrbg_min_seeded = true;
> + pr_info(DRIVER_NAME": primary DRBG fully seeded\n");
Using pr_fmt eliminates the need for these
DRIVER_NAME ": " prefix inclusions in the format
> +static int __init lrng_init(void)
> +{
[]
> + pr_info(DRIVER_NAME": deactivating initial RNG - %d bytes delivered",
> + atomic_read(&lrng_initrng_bytes));
Should use \n to terminate the format.
next prev parent reply other threads:[~2016-04-24 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 10:38 [PATCH v2 0/6] /dev/random - a new approach Stephan Mueller
2016-04-24 10:39 ` [PATCH v2 1/6] crypto: DRBG - externalize DRBG functions for LRNG Stephan Mueller
2016-04-24 10:40 ` [PATCH v2 2/6] random: conditionally compile code depending on LRNG Stephan Mueller
2016-04-24 10:40 ` [PATCH v2 3/6] crypto: Linux Random Number Generator Stephan Mueller
2016-04-24 11:30 ` Joe Perches [this message]
2016-04-24 14:12 ` Stephan Mueller
2016-04-24 16:43 ` Joe Perches
2016-04-24 10:42 ` [PATCH v2 4/6] crypto: LRNG - enable compile Stephan Mueller
2016-04-24 10:42 ` [PATCH v2 5/6] crypto: LRNG - hook LRNG into interrupt handler Stephan Mueller
2016-04-24 10:44 ` [PATCH v2 6/6] hyperv IRQ handler: trigger LRNG Stephan Mueller
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=1461497424.2726.55.camel@perches.com \
--to=joe@perches.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=jason@lakedaemon.net \
--cc=jsd@av8n.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyinchina@gmail.com \
--cc=smueller@chronox.de \
--cc=tytso@mit.edu \
/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).