From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Kashyap Chamarthy <kchamart@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Amit Shah <amit@kernel.org>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org,
"Richard W . M . Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] rng-builtin: add an RNG backend that uses qemu_guest_getrandom()
Date: Fri, 10 May 2019 16:32:27 +0100 [thread overview]
Message-ID: <20190510153227.GO7671@redhat.com> (raw)
In-Reply-To: <87991c2b-da9d-0e7f-bc09-9fbadbda4ef8@redhat.com>
On Fri, May 10, 2019 at 02:37:41PM +0200, Laurent Vivier wrote:
> On 10/05/2019 14:27, Markus Armbruster wrote:
> > Laurent Vivier <lvivier@redhat.com> writes:
> > The new rng-builtin is considerably simpler than both rng-random and
> > rng-egd. Moreover, it just works, whereas rng-random is limited to
> > CONFIG_POSIX, and rng-egd needs egd running (which I suspect basically
> > nobody does). Have we considered deprecating these two backends in
> > favor of rng-builtin?
>
> I have several bugzilla involving these backends: as there are blocking, the
> virtio-rng device in the guest can hang, or crash during hot-unplug. From my
> point of view, life would be easier without them...
Are you sure about that ?
The EGD impl looks like it is requesting entropy in an async manner.
Any problem with rng-random would also affect rng-builtin, as depending
on platform / build options, rng-builtin may just use /dev/urandom
directly. It should only block with /dev/random really and that's only
with Linux's impl of /dev/random - some OS effectively have /dev/random
behave identically to /dev/urandom.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-05-10 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 10:26 [Qemu-devel] [PATCH v2] rng-builtin: add an RNG backend that uses qemu_guest_getrandom() Laurent Vivier
2019-05-10 11:36 ` Daniel P. Berrangé
2019-05-10 12:27 ` Markus Armbruster
2019-05-10 12:37 ` Laurent Vivier
2019-05-10 15:19 ` Markus Armbruster
2019-05-13 16:40 ` Amit Shah
2019-05-10 15:32 ` Daniel P. Berrangé [this message]
2019-05-10 15:56 ` Laurent Vivier
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=20190510153227.GO7671@redhat.com \
--to=berrange@redhat.com \
--cc=amit@kernel.org \
--cc=armbru@redhat.com \
--cc=kchamart@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=rjones@redhat.com \
/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.