From: Ard Biesheuvel <ardb+git@google.com>
To: linux-hardening@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Kees Cook <kees@kernel.org>, Ryan Roberts <ryan.roberts@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Jeremy Linton <jeremy.linton@arm.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [RFC/RFT PATCH 3/6] random: Use u32 to keep track of batched entropy generation
Date: Thu, 27 Nov 2025 10:22:30 +0100 [thread overview]
Message-ID: <20251127092226.1439196-11-ardb+git@google.com> (raw)
In-Reply-To: <20251127092226.1439196-8-ardb+git@google.com>
From: Ard Biesheuvel <ardb@kernel.org>
The batched entropy containers each have a generation field, to keep
track of the base_crng generation from which it was last reseeded.
This use case does not require all bits of the unsigned long to be
stored: storing only 32 bits is sufficient to determine whether or not
we're at most 4 billion generations behind, which seems ample.
So use an unsigned int instead: this will allow a future patch to treat
the generation and position as a single 64-bit quantity, which can be
used locklessly in a compare-and-exchange() operation.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
---
drivers/char/random.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/char/random.c b/drivers/char/random.c
index b8b24b6ed3fe..0e04bc60d034 100644
--- a/drivers/char/random.c
+++ b/drivers/char/random.c
@@ -507,7 +507,7 @@ struct batch_ ##type { \
*/ \
type entropy[CHACHA_BLOCK_SIZE * 3 / (2 * sizeof(type))]; \
local_lock_t lock; \
- unsigned long generation; \
+ unsigned int generation; \
unsigned int position; \
}; \
\
@@ -521,7 +521,7 @@ type get_random_ ##type(void) \
type ret; \
unsigned long flags; \
struct batch_ ##type *batch; \
- unsigned long next_gen; \
+ unsigned int next_gen; \
\
warn_unseeded_randomness(); \
\
@@ -533,7 +533,7 @@ type get_random_ ##type(void) \
local_lock_irqsave(&batched_entropy_ ##type.lock, flags); \
batch = raw_cpu_ptr(&batched_entropy_##type); \
\
- next_gen = READ_ONCE(base_crng.generation); \
+ next_gen = (unsigned int)READ_ONCE(base_crng.generation); \
if (batch->position >= ARRAY_SIZE(batch->entropy) || \
next_gen != batch->generation) { \
_get_random_bytes(batch->entropy, sizeof(batch->entropy)); \
--
2.52.0.107.ga0afd4fd5b-goog
next prev parent reply other threads:[~2025-11-27 9:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 9:22 [RFC/RFT PATCH 0/6] Improve get_random_u8() for use in randomize kstack Ard Biesheuvel
2025-11-27 9:22 ` [RFC/RFT PATCH 1/6] hexagon: Wire up cmpxchg64_local() to generic implementation Ard Biesheuvel
2025-11-27 9:22 ` [RFC/RFT PATCH 2/6] arc: " Ard Biesheuvel
2025-11-27 15:06 ` Joey Gouly
2025-12-03 16:59 ` Ard Biesheuvel
2025-11-27 9:22 ` Ard Biesheuvel [this message]
2025-11-27 10:11 ` [RFC/RFT PATCH 3/6] random: Use u32 to keep track of batched entropy generation david laight
2025-11-27 10:15 ` Ard Biesheuvel
2025-11-27 9:22 ` [RFC/RFT PATCH 4/6] random: Use a lockless fast path for get_random_uXX() Ard Biesheuvel
2025-11-27 10:32 ` Ard Biesheuvel
2025-11-27 9:22 ` [RFC/RFT PATCH 5/6] random: Plug race in preceding patch Ard Biesheuvel
2025-11-28 11:13 ` david laight
2025-11-28 11:18 ` Ard Biesheuvel
2025-11-27 9:22 ` [RFC/RFT PATCH 6/6] randomize_kstack: Use get_random_u8() at entry for entropy Ard Biesheuvel
2025-11-27 12:12 ` [RFC/RFT PATCH 0/6] Improve get_random_u8() for use in randomize kstack Ryan Roberts
2025-11-27 12:28 ` Ard Biesheuvel
2025-11-27 13:08 ` Ryan Roberts
2025-11-27 14:18 ` Ryan Roberts
2025-11-27 15:03 ` Ard Biesheuvel
2025-11-27 15:40 ` Ard Biesheuvel
2025-11-27 15:56 ` Ryan Roberts
2025-11-27 16:58 ` Mark Rutland
2025-11-27 19:01 ` Ard Biesheuvel
2025-11-28 10:36 ` Ryan Roberts
2025-11-28 11:44 ` Mark Rutland
2025-11-28 10:07 ` Ard Biesheuvel
2025-11-28 10:32 ` Ryan Roberts
2025-11-28 10:36 ` Ard Biesheuvel
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=20251127092226.1439196-11-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=Catalin.Marinas@arm.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=jeremy.linton@arm.com \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@arm.com \
--cc=will@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).