From: Laurent Vivier <lvivier@redhat.com>
To: "Daniel P. Berrangé" <berrange@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 17:56:29 +0200 [thread overview]
Message-ID: <a19fde61-159e-45da-f652-1dbc1f94b9ee@redhat.com> (raw)
In-Reply-To: <20190510153227.GO7671@redhat.com>
On 10/05/2019 17:32, Daniel P. Berrangé wrote:
> 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.
The virtio-rng driver waits until it receives enough entropy from the
RNG backend while a mutex is taken.
If the EGD daemon doesn't provide enough data to the RNG backend,
virtio-rng driver can hang.
It's easy to have if we start EGD backend with a socket in server,nowait
mode and no EGD daemon connects to the port.
Thanks,
Laurent
prev parent reply other threads:[~2019-05-10 15:59 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é
2019-05-10 15:56 ` Laurent Vivier [this message]
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=a19fde61-159e-45da-f652-1dbc1f94b9ee@redhat.com \
--to=lvivier@redhat.com \
--cc=amit@kernel.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kchamart@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 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).