From: Noah Meyerhans <noahm@debian.org>
To: stable@vger.kernel.org
Subject: Please apply 50ee7529ec45 ("random: try to actively add entropy rather than passively wait for it") to 4.19.y
Date: Mon, 27 Jan 2020 18:02:14 -0500 [thread overview]
Message-ID: <20200127230214.GC25530@morgul.net> (raw)
As detailed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948519 and
https://wiki.debian.org/BoottimeEntropyStarvation, lack of boot-time entropy
can contribute to multi-minute pauses during system initialization in some
hardware configurations. While userspace workarounds, e.g. haveged, are
documented, the in-kernel jitter entropy collector eliminates the need for such
workarounds.
It cherry-picks cleanly to 4.19.y and 4.14.y. I'm particularly interested
in the former.
Thanks for considering this.
noah
next reply other threads:[~2020-01-27 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 23:02 Noah Meyerhans [this message]
2020-01-28 7:52 ` Please apply 50ee7529ec45 ("random: try to actively add entropy rather than passively wait for it") to 4.19.y Greg KH
2020-01-28 19:34 ` Noah Meyerhans
2020-01-28 19:59 ` Linus Torvalds
2020-01-30 0:39 ` Theodore Y. Ts'o
2020-01-30 14:49 ` Greg KH
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=20200127230214.GC25530@morgul.net \
--to=noahm@debian.org \
--cc=stable@vger.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).