Re: [kernel-hardening] [PATCH v4 05/13] crypto/rng: ensure that the RNG is ready before using

From	"Jason A. Donenfeld" <Jason@zx2c4.com>
Newsgroups	linux.kernel
Subject	Re: [kernel-hardening] [PATCH v4 05/13] crypto/rng: ensure that the RNG is ready before using
Date	2017-06-08 02:50 +0200
Message-ID	<tPTO9-5uW-5@gated-at.bofh.it> (permalink)
References	<tPqM9-3tE-3@gated-at.bofh.it> <tPqVR-3xj-33@gated-at.bofh.it> <tPTO9-5uW-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Thu, Jun 8, 2017 at 2:41 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> The use in keys/big_key is _being_ removed, so this commit is
> dependent on that commit landing, correct?  (Order matters, because
> otherwise we don't want to potentially screw up doing a kernel bisect
> and causing their kernel to deadlock during the boot while they are
> trying to track down an unreleated problem.)

Yes. It's actually landing with get_random_bytes, to avoid a
dependency problem when merging. After these both lands, I'll submit a
third changing that over to get_random_bytes_wait in the right place.

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [kernel-hardening] [PATCH v4 05/13] crypto/rng: ensure that the  RNG is ready before using "Jason A. Donenfeld" <Jason@zx2c4.com> - 2017-06-08 02:50 +0200

csiph-web