From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] random number generator fixes for 6.1-rc3
Date: Sun, 30 Oct 2022 01:49:29 +0200 [thread overview]
Message-ID: <20221029234929.834356-1-Jason@zx2c4.com> (raw)
Hi Linus,
This pull contains one fix from Jean-Philippe Brucker, addressing a regression
in which early boot code on ARM64 would use the non-_early variant of the
arch_get_random family of functions, resulting in the architectural random
number generator appearing unavailable during that early phase of boot. The
fix simply changes arch_get_random*() to arch_get_random*_early().
This distinction between these two functions is a bit of an old wart I'm not a
fan of, and for 6.2 I'll see if I can make obsolete the _early variant, so
that one function does the right thing in all contexts without overhead.
Regards,
Jason
The following changes since commit 23758867219c8d84c8363316e6dd2f9fd7ae3049:
Merge tag 'net-6.1-rc3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2022-10-27 13:36:59 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git tags/random-6.1-rc3-for-linus
for you to fetch changes up to f5e4ec155d145002fd9840868453d785fab86d42:
random: use arch_get_random*_early() in random_init() (2022-10-29 00:24:03 +0200)
----------------------------------------------------------------
Random number generator fixes for Linux 6.1-rc3.
----------------------------------------------------------------
Jean-Philippe Brucker (1):
random: use arch_get_random*_early() in random_init()
drivers/char/random.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2022-10-29 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 23:49 Jason A. Donenfeld [this message]
2022-10-30 1:36 ` pr-tracker-bot
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=20221029234929.834356-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®