On Sat, May 19, 2018 at 05:55:19PM -0400, Theodore Y. Ts'o wrote:
>
> Out of curiosity, how/when were you using RNDCLEARPOOL/RNDZAPENTCNT?
> Hopefully it was only testing hw_random drivers, or some such?
I wasn't actually using it myself. Someone else filed a bug
against RHEL complaining about th
On Fri, May 18, 2018 at 02:57:36PM +0800, Herbert Xu wrote:
> As it is when the pool is zapped with RNDCLEARPOOL writers are
> not woken up and therefore the pool may remain in the empty state
> indefinitely.
>
> This patch wakes them up unless the write threshold is set to zero.
>
> Signed-off-b
As it is when the pool is zapped with RNDCLEARPOOL writers are
not woken up and therefore the pool may remain in the empty state
indefinitely.
This patch wakes them up unless the write threshold is set to zero.
Signed-off-by: Herbert Xu
diff --git a/drivers/char/random.c b/drivers/char/random.c
3 matches
Mail list logo
