All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Michael S. Tsirkin" <mst@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 v3 0/3] rng-builtin: add an RNG backend that uses qemu_guest_getrandom()
Date: Mon, 13 May 2019 14:13:46 +0200	[thread overview]
Message-ID: <871s128scl.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190513084945.GA15247@paraplu> (Kashyap Chamarthy's message of "Mon, 13 May 2019 10:49:45 +0200")

Kashyap Chamarthy <kchamart@redhat.com> writes:

> On Mon, May 13, 2019 at 08:36:23AM +0200, Laurent Vivier wrote:
>> On 12/05/2019 20:21, Michael S. Tsirkin wrote:
>
> [...]
>
>> > > Kashyap Chamarthy (1):
>> > >    VirtIO-RNG: Update default entropy source to `/dev/urandom`
>> > > 
>> > > Laurent Vivier (2):
>> > >    rng-builtin: add an RNG backend that uses qemu_guest_getrandom()
>> > >    virtio-rng: change default backend to rng-builtin
>> > 
>> > 
>> > OK pls address Marku's comment on commit msg and I will merge.
>> 
>> Kashyap,
>> 
>> as this patch is from you, do you agree?
>
> Yes.
>
>> If so, I can update the message and send a new version of the series
>> (or you canr esend your patch alone if you prefer).
>
> Please go ahead and add it, the below is the text (from Dan/Markus):
>
>     What about other OSes?
>     ----------------------
>     
>     `/dev/urandom` exists and works on OS-X, FreeBSD, DragonFlyBSD, NetBSD
>     and OpenBSD, which cover all the non-Linux platforms we explicitly
>     support, aside from Windows.
>     
>     On Windows `/dev/random` doesn't work either so we don't regress.
>     This is actually another argument in favour of using the newly
>     proposed 'rng-builtin' backend by default, as that will work on
>     Windows.

Additionally, please insert "on Linux" into the first paragraph, like
this:

  When QEMU exposes a VirtIO-RNG device to the guest, that device needs a
  source of entropy, and that source needs to be "non-blocking", like
  `/dev/urandom`.  However, currently QEMU defaults to the problematic
  `/dev/random`, which on Linux is "blocking" (as in, it waits until
  sufficient entropy is available).


      reply	other threads:[~2019-05-13 12:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 13:42 [Qemu-devel] [PATCH v3 0/3] rng-builtin: add an RNG backend that uses qemu_guest_getrandom() Laurent Vivier
2019-05-10 13:42 ` [Qemu-devel] [PATCH v3 1/3] VirtIO-RNG: Update default entropy source to `/dev/urandom` Laurent Vivier
2019-05-10 16:12   ` Michael S. Tsirkin
2019-05-10 16:16     ` Daniel P. Berrangé
2019-05-10 16:21       ` Michael S. Tsirkin
2019-05-10 16:25         ` Daniel P. Berrangé
2019-05-10 16:55           ` Michael S. Tsirkin
2019-05-10 17:11             ` Daniel P. Berrangé
2019-05-10 16:18   ` Markus Armbruster
2019-05-10 13:42 ` [Qemu-devel] [PATCH v3 2/3] rng-builtin: add an RNG backend that uses qemu_guest_getrandom() Laurent Vivier
2019-05-10 13:42 ` [Qemu-devel] [PATCH v3 3/3] virtio-rng: change default backend to rng-builtin Laurent Vivier
2019-05-10 16:36   ` Markus Armbruster
2019-05-13 10:26     ` Laurent Vivier
2019-05-14 14:39       ` Markus Armbruster
2019-05-12 18:21 ` [Qemu-devel] [PATCH v3 0/3] rng-builtin: add an RNG backend that uses qemu_guest_getrandom() Michael S. Tsirkin
2019-05-13  6:36   ` Laurent Vivier
2019-05-13  8:49     ` Kashyap Chamarthy
2019-05-13 12:13       ` Markus Armbruster [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=871s128scl.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=amit@kernel.org \
    --cc=berrange@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mst@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.