From: "Theodore Ts'o" <tytso@mit.edu>
To: Stephan Mueller <smueller@chronox.de>,
Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
herbert@gondor.apana.org.au, andi@firstfloor.org,
sandyinchina@gmail.com, cryptography@lakedaemon.net,
jsd@av8n.com, hpa@zytor.com, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/4] random: replace non-blocking pool with a Chacha20-based CRNG
Date: Thu, 5 May 2016 08:49:06 -0400 [thread overview]
Message-ID: <20160505124906.GF10776@thunk.org> (raw)
In-Reply-To: <20160505011007.GB10776@thunk.org>
On Wed, May 04, 2016 at 09:10:07PM -0400, Theodore Ts'o wrote:
> On Wed, May 04, 2016 at 10:28:24PM +0200, Stephan Mueller wrote:
> > > +out:
> > > + spin_unlock_irqrestore(&primary_crng.lock, flags);
> > > + return ret;
> >
> > Where did you add the memzero_explict of tmp?
>
> Oops, sorry, somehow that change got lost in the patch updates. Fixed now.
Since that was the only change, instead of sending out the patch
series again, I've just updated it at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git dev
- Ted
next prev parent reply other threads:[~2016-05-05 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 19:25 [PATCH -v2 0/4] random: replace urandom pool with a CRNG Theodore Ts'o
2016-05-04 19:25 ` [PATCH 1/4] random: replace non-blocking pool with a Chacha20-based CRNG Theodore Ts'o
2016-05-04 20:28 ` Stephan Mueller
2016-05-05 1:10 ` Theodore Ts'o
2016-05-05 12:49 ` Theodore Ts'o [this message]
2016-05-04 19:25 ` [PATCH 2/4] random: make /dev/urandom scalable for silly userspace programs Theodore Ts'o
2016-05-04 19:25 ` [PATCH 3/4] random: add interrupt callback to VMBus IRQ handler Theodore Ts'o
2016-05-04 19:25 ` [PATCH 4/4] random: add backtracking protection to the CRNG Theodore Ts'o
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=20160505124906.GF10776@thunk.org \
--to=tytso@mit.edu \
--cc=andi@firstfloor.org \
--cc=cryptography@lakedaemon.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=jsd@av8n.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyinchina@gmail.com \
--cc=smueller@chronox.de \
/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