From: Eric Biggers <ebiggers@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, linux@dominikbrodowski.net,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH v2 01/10] random: introduce drain_entropy() helper to declutter crng_reseed()
Date: Sun, 20 Feb 2022 20:34:19 -0800 [thread overview]
Message-ID: <YhMWS+gxKdrQIFwo@sol.localdomain> (raw)
In-Reply-To: <20220212122318.623435-2-Jason@zx2c4.com>
On Sat, Feb 12, 2022 at 01:23:09PM +0100, Jason A. Donenfeld wrote:
> In preparation for separating responsibilities, break out the entropy
> count management part of crng_reseed() into its own function.
>
> No functional changes.
>
> Cc: Theodore Ts'o <tytso@mit.edu>
> Cc: Dominik Brodowski <linux@dominikbrodowski.net>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> drivers/char/random.c | 35 +++++++++++++++++++++++------------
> 1 file changed, 23 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/char/random.c b/drivers/char/random.c
> index 44a20a1a1b3a..436b146b33be 100644
> --- a/drivers/char/random.c
> +++ b/drivers/char/random.c
> @@ -260,6 +260,7 @@ static struct {
> };
>
> static void extract_entropy(void *buf, size_t nbytes);
> +static bool drain_entropy(void *buf, size_t nbytes);
>
> static void crng_reseed(void);
>
> @@ -453,22 +454,13 @@ static void crng_slow_load(const void *cp, size_t len)
> static void crng_reseed(void)
> {
> unsigned long flags;
> - int entropy_count;
> unsigned long next_gen;
> u8 key[CHACHA_KEY_SIZE];
> bool finalize_init = false;
>
> - /* First we make sure we have POOL_MIN_BITS of entropy in the pool,
> - * and then we drain all of it. Only then can we extract a new key.
> - */
> - do {
> - entropy_count = READ_ONCE(input_pool.entropy_count);
> - if (entropy_count < POOL_MIN_BITS)
> - return;
> - } while (cmpxchg(&input_pool.entropy_count, entropy_count, 0) != entropy_count);
> - extract_entropy(key, sizeof(key));
> - wake_up_interruptible(&random_write_wait);
> - kill_fasync(&fasync, SIGIO, POLL_OUT);
> + /* Only reseed if we can, to prevent brute forcing a small amount of new bits. */
> + if (!drain_entropy(key, sizeof(key)))
> + return;
>
> /* We copy the new key into the base_crng, overwriting the old one,
> * and update the generation counter. We avoid hitting ULONG_MAX,
> @@ -893,6 +885,25 @@ static void extract_entropy(void *buf, size_t nbytes)
> memzero_explicit(&block, sizeof(block));
> }
>
> +/*
> + * First we make sure we have POOL_MIN_BITS of entropy in the pool,
> + * and then we drain all of it. Only then can we extract a new key
> + * with extract_entropy().
> + */
> +static bool drain_entropy(void *buf, size_t nbytes)
> +{
> + unsigned int entropy_count;
> + do {
> + entropy_count = READ_ONCE(input_pool.entropy_count);
> + if (entropy_count < POOL_MIN_BITS)
> + return false;
> + } while (cmpxchg(&input_pool.entropy_count, entropy_count, 0) != entropy_count);
> + extract_entropy(buf, nbytes);
> + wake_up_interruptible(&random_write_wait);
> + kill_fasync(&fasync, SIGIO, POLL_OUT);
> + return true;
> +}
Looks good, but perhaps the comment should clarify that drain_entropy() doesn't
destroy the entropy in the pool, but rather just extracts it and zeroes out the
entropy counter?
- Eric
next prev parent reply other threads:[~2022-02-21 4:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 12:23 [PATCH v2 00/10] random: re-group and re-document functions Jason A. Donenfeld
2022-02-12 12:23 ` [PATCH v2 01/10] random: introduce drain_entropy() helper to declutter crng_reseed() Jason A. Donenfeld
2022-02-21 4:34 ` Eric Biggers [this message]
2022-02-21 14:49 ` Jason A. Donenfeld
2022-02-21 14:49 ` [PATCH v3] " Jason A. Donenfeld
2022-02-21 19:19 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 02/10] random: remove useless header comment Jason A. Donenfeld
2022-02-21 4:34 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 03/10] random: remove whitespace and reorder includes Jason A. Donenfeld
2022-02-21 4:35 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 04/10] random: group initialization wait functions Jason A. Donenfeld
2022-02-13 6:54 ` Dominik Brodowski
2022-02-13 13:11 ` Jason A. Donenfeld
2022-02-21 4:49 ` Eric Biggers
2022-02-21 15:10 ` Jason A. Donenfeld
2022-02-21 15:14 ` [PATCH v3] " Jason A. Donenfeld
2022-02-21 19:20 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 05/10] random: group crng functions Jason A. Donenfeld
2022-02-13 6:54 ` Dominik Brodowski
2022-02-13 13:14 ` Jason A. Donenfeld
2022-02-21 5:00 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 06/10] random: group entropy extraction functions Jason A. Donenfeld
2022-02-21 5:05 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 07/10] random: group entropy collection functions Jason A. Donenfeld
2022-02-13 6:54 ` Dominik Brodowski
2022-02-13 13:16 ` Jason A. Donenfeld
2022-02-21 5:13 ` Eric Biggers
2022-02-21 15:17 ` Jason A. Donenfeld
2022-02-21 15:18 ` [PATCH v3] " Jason A. Donenfeld
2022-02-21 19:23 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 08/10] random: group userspace read/write functions Jason A. Donenfeld
2022-02-21 5:16 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 09/10] random: group sysctl functions Jason A. Donenfeld
2022-02-21 5:21 ` Eric Biggers
2022-02-21 15:27 ` Jason A. Donenfeld
2022-02-21 15:39 ` Jason A. Donenfeld
2022-02-12 12:23 ` [PATCH v2 10/10] random: rewrite header introductory comment Jason A. Donenfeld
2022-02-21 5:26 ` Eric Biggers
2022-02-13 6:55 ` [PATCH v2 00/10] random: re-group and re-document functions Dominik Brodowski
2022-02-13 13:07 ` Jason A. Donenfeld
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=YhMWS+gxKdrQIFwo@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--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