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 7.3-rc6
Date: Fri, 2 Oct 2026 16:01:10 +0200 [thread overview]
Message-ID: <20261002140110.1481971-1-Jason@zx2c4.com> (raw)
Hi Linus,
Please pull the following small set of updates to the random number generator
and related code:
- VMGENID memory needs to be mapped with the decrypted tag, so that SEV-SNP
machines can boot.
- A fix for an initialization race in VMGENID, followed by a cleanup.
- Trivial kernel doc cleanups in siphash and random.c. Arguably this isn't a
true bug fix and would be for 7.4, but it's so insignificant, that I figure
it's fine.
- A fix for a new compilation failure with recent clang on PPC and RISC-V, due
to generating an out-of-line memset in the vDSO.
The last fix has a conflict with linux-next, which you might encounter in the
7.4 merge window: https://lore.kernel.org/all/ar5-4Yq3wtmXTWnD@sirena.org.uk/T/#u
Thanks,
Jason
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git tags/random-7.3-rc6-for-linus
for you to fetch changes up to eb13a1ff271b0d180687eebb30611b0b276d5193:
random: vDSO: avoid call to memset() when zeroing reserved parameter (2026-10-02 12:12:13 +0200)
----------------------------------------------------------------
Random number generator fixes for Linux 7.3-rc6.
----------------------------------------------------------------
Hemanth Selam (1):
random: vDSO: fix repeated word 'to' in comment
Jason A. Donenfeld (1):
virt: vmgenid: move to using dev_set/get_drvdata
Karl Mehltretter (1):
random: fix vgetrandom_opaque_params kernel-doc
Nathan Chancellor (1):
random: vDSO: avoid call to memset() when zeroing reserved parameter
Randy Dunlap (1):
siphash: clean up kernel-doc comments
Vitaly Kuznetsov (1):
virt: vmgenid: remap memory as decrypted
Zhichen Wang (1):
virt: vmgenid: set driver_data before registering notification handlers
arch/arm64/kernel/vdso/Makefile | 2 +-
arch/loongarch/vdso/Makefile | 1 +
arch/powerpc/kernel/vdso/Makefile | 1 +
arch/riscv/kernel/vdso/Makefile | 1 +
arch/s390/kernel/vdso/Makefile | 1 +
arch/x86/entry/vdso/vdso64/Makefile | 2 +-
drivers/virt/vmgenid.c | 11 +++++++----
include/linux/siphash.h | 8 ++++++--
include/uapi/linux/random.h | 2 +-
include/vdso/getrandom.h | 2 +-
init/Kconfig | 5 +++++
11 files changed, 26 insertions(+), 10 deletions(-)
next reply other threads:[~2026-10-02 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 14:01 Jason A. Donenfeld [this message]
2026-10-02 19:16 ` 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=20261002140110.1481971-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®