Re: [PATCH 1/5] random: fix crng_ready() test
- Date: Fri, 13 Apr 2018 15:05:01 +0200
- From: Stephan Mueller <smueller@xxxxxxxxxx>
- Subject: Re: [PATCH 1/5] random: fix crng_ready() test
Am Freitag, 13. April 2018, 14:53:13 CEST schrieb Theodore Y. Ts'o:
> This was always the original design intent, but I screwed up and no
> one noticed until Jann reached out to be and said, "Hey.... this
> doesn't seem to make much sense".
I disagree, but I guess you would have expected that. But this is not the
What I would like to point out that more and more folks change to
getrandom(2). As this call will now unblock much later in the boot cycle,
these systems see a significant departure from the current system behavior.
E.g. an sshd using getrandom(2) would be ready shortly after the boot finishes
as of now. Now it can be a matter minutes before it responds. Thus, is such
change in the kernel behavior something for stable?