From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Sultan Alsawaf <sultan@kerneltoast.com>
Subject: [PATCH 2/2] random: spread out jitter callback to different CPUs
Date: Sat, 1 Oct 2022 01:10:50 +0200 [thread overview]
Message-ID: <20220930231050.749824-2-Jason@zx2c4.com> (raw)
In-Reply-To: <20220930231050.749824-1-Jason@zx2c4.com>
Rather than merely hoping that the callback gets called on another CPU,
arrange for that to actually happen, by round robining which CPU the
timer fires on. This way, on multiprocessor machines, we exacerbate
jitter by touching the same memory from multiple different cores.
Cc: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Sultan Alsawaf <sultan@kerneltoast.com>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
---
drivers/char/random.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/drivers/char/random.c b/drivers/char/random.c
index fdf15f5c87dd..74627b53179a 100644
--- a/drivers/char/random.c
+++ b/drivers/char/random.c
@@ -1209,6 +1209,7 @@ static void __cold try_to_generate_entropy(void)
struct entropy_timer_state stack;
unsigned int i, num_different = 0;
unsigned long last = random_get_entropy();
+ int cpu = -1;
for (i = 0; i < NUM_TRIAL_SAMPLES - 1; ++i) {
stack.entropy = random_get_entropy();
@@ -1223,8 +1224,17 @@ static void __cold try_to_generate_entropy(void)
stack.samples = 0;
timer_setup_on_stack(&stack.timer, entropy_timer, 0);
while (!crng_ready() && !signal_pending(current)) {
- if (!timer_pending(&stack.timer))
- mod_timer(&stack.timer, jiffies);
+ if (!timer_pending(&stack.timer)) {
+ preempt_disable();
+ do {
+ cpu = cpumask_next(cpu, cpu_online_mask);
+ if (cpu == nr_cpumask_bits)
+ cpu = cpumask_first(cpu_online_mask);
+ } while (cpu == smp_processor_id() && cpumask_weight(cpu_online_mask) > 1);
+ stack.timer.expires = jiffies;
+ add_timer_on(&stack.timer, cpu);
+ preempt_enable();
+ }
mix_pool_bytes(&stack.entropy, sizeof(stack.entropy));
schedule();
stack.entropy = random_get_entropy();
--
2.37.3
next prev parent reply other threads:[~2022-09-30 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 23:10 [PATCH 1/2] random: schedule jitter credit for next jiffy, not in two jiffies Jason A. Donenfeld
2022-09-30 23:10 ` Jason A. Donenfeld [this message]
2022-10-01 9:21 ` [PATCH 2/2] random: spread out jitter callback to different CPUs Jason A. Donenfeld
2022-10-05 17:26 ` Sebastian Andrzej Siewior
2022-10-05 21:08 ` Jason A. Donenfeld
2022-10-06 6:46 ` Sebastian Andrzej Siewior
2022-10-06 12:26 ` Jason A. Donenfeld
2022-10-06 12:41 ` Sebastian Andrzej Siewior
2022-10-06 16:39 ` Sultan Alsawaf
2022-10-07 7:29 ` Sebastian Andrzej Siewior
2022-10-07 14:01 ` Jason A. Donenfeld
2022-10-07 14:55 ` Sebastian Andrzej Siewior
2022-10-07 15:32 ` Jason A. Donenfeld
2022-11-29 16:08 ` [PATCH v2] " Jason A. Donenfeld
2022-11-29 18:27 ` [PATCH v3] " Jason A. Donenfeld
[not found] ` <20221130014514.6494-1-hdanton@sina.com>
2022-11-30 1:49 ` Jason A. Donenfeld
2022-11-30 18:48 ` [PATCH v4] " 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=20220930231050.749824-2-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=bigeasy@linutronix.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=sultan@kerneltoast.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
Powered by JetHome