From: "Theodore Ts'o" <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] random changes for 5.2
Date: Tue, 7 May 2019 19:32:08 -0400 [thread overview]
Message-ID: <20190507233208.GA28817@mit.edu> (raw)
The following changes since commit dc4060a5dc2557e6b5aa813bf5b73677299d62d2:
Linux 5.1-rc5 (2019-04-14 15:17:41 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/random_for_linus
for you to fetch changes up to b7d5dc21072cda7124d13eae2aefb7343ef94197:
random: add a spinlock_t to struct batched_entropy (2019-04-20 00:09:56 -0400)
----------------------------------------------------------------
Initialize the random driver earler; fix CRNG initialization when we
trust the CPU's RNG on NUMA systems; other miscellaneous cleanups and
fixes.
----------------------------------------------------------------
George Spelvin (1):
random: document get_random_int() family
Jon DeVree (1):
random: fix CRNG initialization when random.trust_cpu=1
Kees Cook (1):
random: move rand_initialize() earlier
Rasmus Villemoes (3):
drivers/char/random.c: constify poolinfo_table
drivers/char/random.c: remove unused stuct poolinfo::poolbits
drivers/char/random.c: make primary_crng static
Sebastian Andrzej Siewior (1):
random: add a spinlock_t to struct batched_entropy
Theodore Ts'o (1):
random: only read from /dev/random after its pool has received 128 bits
drivers/char/random.c | 199 +++++++++++++++++++++++++++++++++++++++++++++---------------------
include/linux/random.h | 1 +
include/trace/events/random.h | 13 ++---
init/main.c | 21 ++++---
4 files changed, 156 insertions(+), 78 deletions(-)
next reply other threads:[~2019-05-07 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 23:32 Theodore Ts'o [this message]
2019-05-08 4:55 ` [GIT PULL] random changes for 5.2 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=20190507233208.GA28817@mit.edu \
--to=tytso@mit.edu \
--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