Re: [PATCH v5 1/5] random: Async and sync API for accessing nonblocking_pool

On Mon, May 11, 2015 at 09:30:11AM +0200, Stephan Mueller wrote: > > I will remove that in the next installment. But that means that the DRBG > kernel module (or any other module) cannot be unloaded until the work > completes. I don't think that's a big deal. > Are you suggesting to only leave

Re: [PATCH v5 1/5] random: Async and sync API for accessing nonblocking_pool

Am Montag, 11. Mai 2015, 14:57:14 schrieb Herbert Xu: Hi Herbert, > >There are two problems with this patch: > >1) The interface is way too complicated for a once off wait used >only during boot. Really there is no need for cancellations. I will remove that in the next installment. But that mean

Re: [PATCH v5 1/5] random: Async and sync API for accessing nonblocking_pool

On Fri, May 08, 2015 at 08:41:30AM +0200, Stephan Mueller wrote: > The added API calls provide a synchronous function call > get_blocking_random_bytes where the caller is blocked until > the nonblocking_pool is initialized. > > In addition, an asynchronous API call of get_blocking_random_bytes_cb

[PATCH v5 1/5] random: Async and sync API for accessing nonblocking_pool

The added API calls provide a synchronous function call get_blocking_random_bytes where the caller is blocked until the nonblocking_pool is initialized. In addition, an asynchronous API call of get_blocking_random_bytes_cb is provided which returns immediately to the caller after submitting the re