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

From: Herbert Xu
Date: Mon May 11 2015 - 05:28:51 EST

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 get_blocking_random_bytes and have the caller
> implementing the appropriate synchronous wait or async work?

No there should just be a single interface where you feed it a
function pointer and a data pointer. This function should then
be called when the pool is ready.

Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page:
PGP Key:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at