[lkml]   [2015]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [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 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 <>
Home Page:
PGP Key:

 \ /
  Last update: 2015-05-11 12:01    [W:0.035 / U:19.536 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site