From: Ben Hutchings <ben@decadent.org.uk>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
kvm@vger.kernel.org, Ian Molton <ian.molton@collabora.co.uk>,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: virtio-rng only returns zeros with CONFIG_HW_RANDOM=m
Date: Wed, 27 Feb 2013 03:40:37 +0000 [thread overview]
Message-ID: <1361936437.3768.56.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <8738wifwb2.fsf@rustcorp.com.au>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
On Wed, 2013-02-27 at 10:43 +1030, Rusty Russell wrote:
> Aurelien Jarno <aurelien@aurel32.net> writes:
> > Hi,
> >
> > I have noticed that virtio-rng only returns zero for kernels >= 2.6.33
> > built with CONFIG_HW_RANDOM=m. This is a bit much too predictable for a
> > random generator ;-).
>
> Wow. Fortunately, all of SLES, RHEL, Ubuntu or Fedora set
> CONFIG_HW_RANDOM=y. What do they know that we don't?
>
> Oops, looks like Debian testing: config-3.2.0-4-amd64:CONFIG_HW_RANDOM=m
[...]
*Groan*. I'll change the configuration for now, but trust this will be
fixed in virtio-rng later. Thanks for letting me know.
Ben.
--
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-02-27 3:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 23:11 virtio-rng only returns zeros with CONFIG_HW_RANDOM=m Aurelien Jarno
2013-02-27 0:13 ` Rusty Russell
2013-02-27 3:40 ` Ben Hutchings [this message]
2013-02-27 10:33 ` Aurelien Jarno
2013-02-27 13:22 ` Jens Axboe
2013-02-28 3:00 ` Rusty Russell
2013-05-30 1:07 ` Rusty Russell
2013-05-30 7:18 ` Jens Axboe
2013-02-27 1:26 ` Rusty Russell
2013-02-27 16:36 ` Aurelien Jarno
2013-02-28 3:04 ` Rusty Russell
2013-03-10 8:26 ` 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=1361936437.3768.56.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=aurelien@aurel32.net \
--cc=axboe@kernel.dk \
--cc=herbert@gondor.apana.org.au \
--cc=ian.molton@collabora.co.uk \
--cc=kvm@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.