From: Eric Biggers <ebiggers@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, Sultan Alsawaf <sultan@kerneltoast.com>
Subject: Re: [PATCH] random: align entropy_timer_state to cache line
Date: Tue, 29 Nov 2022 20:55:48 -0800 [thread overview]
Message-ID: <Y4biVHVPhVyVJ6Fc@sol.localdomain> (raw)
In-Reply-To: <20221130020815.283814-1-Jason@zx2c4.com>
Hi Jason,
On Wed, Nov 30, 2022 at 03:08:15AM +0100, Jason A. Donenfeld wrote:
> The theory behind the jitter dance is that multiple things are poking at
> the same cache line. This only works, however, if those things are
> actually all in the same cache line. Ensure this is the case by aligning
> the struct on the stack to the cache line size.
>
> On x86, this indeed aligns the stack struct:
>
> 000000000000000c <try_to_generate_entropy>:
> {
> c: 55 push %rbp
> - d: 53 push %rbx
> - e: 48 83 ec 38 sub $0x38,%rsp
> + d: 48 89 e5 mov %rsp,%rbp
> + 10: 41 54 push %r12
> + 12: 53 push %rbx
> + 13: 48 83 e4 c0 and $0xffffffffffffffc0,%rsp
> + 17: 48 83 ec 40 sub $0x40,%rsp
>
> Cc: Sultan Alsawaf <sultan@kerneltoast.com>
> Fixes: 50ee7529ec45 ("random: try to actively add entropy rather than passively wait for it")
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> drivers/char/random.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/random.c b/drivers/char/random.c
> index 67558b95d531..2494e08c76d8 100644
> --- a/drivers/char/random.c
> +++ b/drivers/char/random.c
> @@ -1262,7 +1262,7 @@ static void __cold entropy_timer(struct timer_list *timer)
> static void __cold try_to_generate_entropy(void)
> {
> enum { NUM_TRIAL_SAMPLES = 8192, MAX_SAMPLES_PER_BIT = HZ / 15 };
> - struct entropy_timer_state stack;
> + struct entropy_timer_state stack ____cacheline_aligned;
Several years ago, there was a whole thing about how __attribute__((aligned)) to
more than 8 bytes doesn't actually work on stack variables in the kernel on x86,
because the kernel only keeps the stack 8-byte aligned but gcc assumes it is
16-byte aligned. See
https://lore.kernel.org/linux-crypto/20170110143340.GA3787@gondor.apana.org.au/T/#t
IIRC, nothing was done about it at the time.
Has that been resolved in the intervening years?
- Eric
next prev parent reply other threads:[~2022-11-30 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 2:08 Jason A. Donenfeld
2022-11-30 4:55 ` Eric Biggers [this message]
2022-11-30 10:04 ` Jason A. Donenfeld
2022-11-30 18:59 ` Eric Biggers
2022-11-30 19:31 ` Jason A. Donenfeld
2022-11-30 19:51 ` Eric Biggers
2022-11-30 19:54 ` Jason A. Donenfeld
2022-11-30 20:02 ` [PATCH v2] " 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=Y4biVHVPhVyVJ6Fc@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®