public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: random: Wake up writers when random pools are zapped
Date: Sat, 19 May 2018 17:55:19 -0400	[thread overview]
Message-ID: <20180519215519.GA23448@thunk.org> (raw)
In-Reply-To: <20180518065736.szvspgdeyiaiqheb@gondor.apana.org.au>

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-by: Herbert Xu <herbert@gondor.apana.org.au>

Thanks, applied.

Out of curiosity, how/when were you using RNDCLEARPOOL/RNDZAPENTCNT?
Hopefully it was only testing hw_random drivers, or some such?

	     	      	      		- Ted

  reply	other threads:[~2018-05-19 21:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  6:57 random: Wake up writers when random pools are zapped Herbert Xu
2018-05-19 21:55 ` Theodore Y. Ts'o [this message]
2018-05-20  3:02   ` Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180519215519.GA23448@thunk.org \
    --to=tytso@mit.edu \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox