This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v3] getrandom system call wrapper [BZ #17252]
- From: Zack Weinberg <zackw at panix dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: Torvald Riegel <triegel at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 12 Oct 2016 12:10:47 -0400
- Subject: Re: [PATCH v3] getrandom system call wrapper [BZ #17252]
- Authentication-results: sourceware.org; auth=none
- References: <661db778-8110-82b2-2c41-d6195916cbea@redhat.com> <1473430905.30192.5.camel@localhost.localdomain> <a93942f0-c688-8d8e-92dc-8fad856838b1@redhat.com> <1473434601.30192.13.camel@localhost.localdomain> <771c9c53-44df-cfdb-1ad2-c7a249b7d6c5@redhat.com> <2997042e-a33a-afbb-79ae-2c04c015dff1@redhat.com>
On Wed, Oct 12, 2016 at 11:58 AM, Florian Weimer <fweimer@redhat.com> wrote:
>>> Can the system call really block indefinitely, or only for a long time
>>> and (ie, will return eventually)?
>>
>> Yes, if the system enters a deadlock condition where the waiting for
>> randomness prevents it from accumulating additional randomness.
>
> This is what happens here:
>
> <https://bugzilla.redhat.com/show_bug.cgi?id=1383060>
... How about we make the kernel not start userspace at all until the
RNG is fully operational?
zw