Re: [PATCH RFC v4 1/1] random: WARN on large getrandom() waits and introduce getrandom2()
From: Florian Weimer <hidden>
Date: 2019-09-21 06:07:44
Also in:
linux-ext4, linux-man, lkml
Possibly related (same subject, not in this thread)
- 2019-09-21 · Re: [PATCH RFC v4 1/1] random: WARN on large getrandom() waits and introduce getrandom2() · Willy Tarreau <w@1wt.eu>
- 2019-09-20 · Re: [PATCH RFC v4 1/1] random: WARN on large getrandom() waits and introduce getrandom2() · Andy Lutomirski <luto@kernel.org>
- 2019-09-20 · Re: [PATCH RFC v4 1/1] random: WARN on large getrandom() waits and introduce getrandom2() · Linus Torvalds <torvalds@linux-foundation.org>
- 2019-09-20 · Re: [PATCH RFC v4 1/1] random: WARN on large getrandom() waits and introduce getrandom2() · Andy Lutomirski <luto@kernel.org>
- 2019-09-20 · Re: [PATCH RFC v4 1/1] random: WARN on large getrandom() waits and introduce getrandom2() · Matthew Garrett <mjg59@srcf.ucam.org>
* Linus Torvalds:
Violently agreed. And that's kind of what the GRND_EXPLICIT is really aiming for. However, it's worth noting that nobody should ever use GRND_EXPLICIT directly. That's just the name for the bit. The actual users would use GRND_INSECURE or GRND_SECURE.
Should we switch glibc's getentropy to GRND_EXPLICIT? Or something else? I don't think we want to print a kernel warning for this function. Thanks, Florian