Messages in this thread | | | From | "Jason A. Donenfeld" <> | Date | Thu, 8 Jun 2017 02:47:36 +0200 | Subject | Re: [kernel-hardening] [PATCH v4 05/13] crypto/rng: ensure that the RNG is ready before using |
| |
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.
| |