From: Herbert Xu <herbert@gondor.apana.org.au>
To: "Theodore Ts'o" <tytso@mit.edu>,
Stephan Mueller <smueller@chronox.de>,
pebolle@tiscali.nl, andreas.steffen@strongswan.org,
sandyinchina@gmail.com, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v6 1/5] random: Blocking API for accessing nonblocking_pool
Date: Tue, 19 May 2015 22:18:05 +0800 [thread overview]
Message-ID: <20150519141805.GA32663@gondor.apana.org.au> (raw)
In-Reply-To: <20150519135028.GC20421@thunk.org>
On Tue, May 19, 2015 at 09:50:28AM -0400, Theodore Ts'o wrote:
>
> Finally, this is only going to block *once*, when the system is
> initially botting up. Why is it so important that we get the
> asynchronous nature of this right, and why can't we solve it simply by
> just simply doing the work in a workqueue, with a completion barrier
> getting triggered once /dev/random initializes itself, and just simply
> blocking the module unload until /dev/random is initialized?
I guess I'm still thinking of the old work queue code before
Tejun's cmwq work. Yes blocking in a work queue should be fine
as there is usually just one DRBG instance.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2015-05-19 14:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 19:54 [PATCH v6 0/5] Seeding DRBG with more entropy Stephan Mueller
2015-05-13 19:54 ` [PATCH v6 1/5] random: Blocking API for accessing nonblocking_pool Stephan Mueller
2015-05-15 6:46 ` Herbert Xu
2015-05-18 5:32 ` Stephan Mueller
2015-05-18 9:21 ` Herbert Xu
2015-05-18 13:07 ` Stephan Mueller
2015-05-18 13:26 ` Stephan Mueller
2015-05-18 15:02 ` Theodore Ts'o
2015-05-19 5:58 ` Stephan Mueller
2015-05-19 7:22 ` Herbert Xu
2015-05-19 7:35 ` Stephan Mueller
2015-05-19 7:51 ` Herbert Xu
2015-05-19 7:56 ` Stephan Mueller
2015-05-19 13:50 ` Theodore Ts'o
2015-05-19 14:18 ` Herbert Xu [this message]
2015-05-19 14:27 ` Stephan Mueller
2015-05-19 14:30 ` Herbert Xu
2015-05-19 14:36 ` Stephan Mueller
2015-05-19 22:55 ` Herbert Xu
2015-05-20 6:13 ` Stephan Mueller
2015-06-05 5:28 ` Herbert Xu
2015-06-05 9:50 ` Stephan Mueller
2015-05-13 19:55 ` [PATCH v6 2/5] crypto: drbg - prepare for async seeding Stephan Mueller
2015-05-13 19:55 ` [PATCH v6 3/5] crypto: drbg - add async seeding operation Stephan Mueller
2015-05-13 19:56 ` [PATCH v6 4/5] crypto: drbg - use Jitter RNG to obtain seed Stephan Mueller
2015-05-13 19:56 ` [PATCH v6 5/5] crypto: add jitterentropy RNG Stephan Mueller
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=20150519141805.GA32663@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=andreas.steffen@strongswan.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=sandyinchina@gmail.com \
--cc=smueller@chronox.de \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).