Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 8 Jun 2017 02:47:36 +0200
From: "Jason A. Donenfeld" <>
To: "Theodore Ts'o" <>, "Jason A. Donenfeld" <>, 
	Linux Crypto Mailing List <>, LKML <>,, 
	Greg Kroah-Hartman <>, David Miller <>, 
	Eric Biggers <>, Herbert Xu <>
Subject: Re: [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 <> 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.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.