From: "Stephan Müller" <smueller@chronox.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-kernel@vger.kernel.org,
Javier Martinez Canillas <javier@osg.samsung.com>,
Kukjin Kim <kgene@kernel.org>,
linux-crypto@vger.kernel.org, Matt Mackall <mpm@selenic.com>,
Olof Johansson <olof@lixom.net>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] crypto: hw_random - Add new Exynos RNG driver
Date: Sat, 25 Mar 2017 13:48:35 +0100 [thread overview]
Message-ID: <2198038.IahjPeE5Ux@positron.chronox.de> (raw)
In-Reply-To: <20170325073648.cbphcouvi6trmhcj@kozik-lap>
Am Samstag, 25. März 2017, 08:36:48 CET schrieb Krzysztof Kozlowski:
Hi Krzysztof,
> On Fri, Mar 24, 2017 at 09:41:59PM +0100, Stephan Müller wrote:
> > Am Freitag, 24. März 2017, 19:26:04 CET schrieb Krzysztof Kozlowski:
> >
> > Hi Krzysztof,
> >
> > > +static unsigned int exynos_rng_copy_random(struct exynos_rng_dev *rng,
> > > + u8 *dst, unsigned int dlen)
> > > +{
> > > + unsigned int cnt = 0;
> > > + int i, j;
> > > + u32 val;
> > > +
> > > + for (j = 0; j < EXYNOS_RNG_SEED_REGS; j++) {
> > > + val = exynos_rng_readl(rng, EXYNOS_RNG_OUT(j));
> > > +
> > > + for (i = 0; i < 4; i++) {
> > > + dst[cnt] = val & 0xff;
> > > + val >>= 8;
> > > + if (++cnt >= dlen)
> > > + return cnt;
> > > + }
> > > + rng->seed_save[j] = val;
> >
> > Just to clarify: is this call right? Shouldn't that be removed? Any RNG
> > that is given to a caller is tainted and should not serve as seed.
>
> In that case I could either re-use RNGs not passed to the caller (like
> in the block quoted below) or generate another round of them just for
> purpose of next seeding.
>
> With the first approach the problem is that I might wait for such unused
> numbers pretty long. If user is requesting large amount of data, then I
> will always give him all five output numbers. I will not have unused
> numbers.
>
> The second approach seems safe, but requires additional engine run which
> will slow down some of the generate() calls.
Random numbers should never be used twice.
>
> > > + }
> > > +
> > > + /*
> > > + * Engine filled all output registers, so read the remaining registers
> > > + * for storing data as future seed.
> > > + */
> > > + for (; j < EXYNOS_RNG_SEED_REGS; j++)
> > > + rng->seed_save[j] = exynos_rng_readl(rng, EXYNOS_RNG_OUT(j));
> >
> > With this call, I guess the questioned line above could go away, right?
>
> This is used in combination with the previous line so I will get five
> seeds (for five registers).
>
> Best regards,
> Krzysztof
Ciao
Stephan
next prev parent reply other threads:[~2017-03-25 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 18:26 [PATCH v2 0/3] crypto: hw_random - Add new Exynos RNG driver Krzysztof Kozlowski
2017-03-24 18:26 ` [PATCH v2 1/3] " Krzysztof Kozlowski
2017-03-24 20:41 ` Stephan Müller
2017-03-25 7:36 ` Krzysztof Kozlowski
2017-03-25 12:48 ` Stephan Müller [this message]
2017-03-24 18:26 ` [PATCH v2 2/3] ARM: exynos_defconfig: Enable Exynos RNG and user-space crypto API Krzysztof Kozlowski
2017-03-24 18:26 ` [PATCH v2 3/3] ARM: multi_v7_defconfig: " Krzysztof Kozlowski
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=2198038.IahjPeE5Ux@positron.chronox.de \
--to=smueller@chronox.de \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=olof@lixom.net \
/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