From: Thomas Huth <1811758@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1811758] Re: virtio-rng backend should use getentropy() syscall when available
Date: Tue, 16 Apr 2019 05:37:26 -0000 [thread overview]
Message-ID: <155539304622.13876.14766283166073144058.malone@gac.canonical.com> (raw)
In-Reply-To: 154753485996.31938.10842883255904010357.malonedeb@wampee.canonical.com
Feel free to send some patches to implement this! Alternatively, you
could also try to write a mail to the virtio-rng maintainer (see the
MAINTAINER file in the top directory of the sources), maybe he can help.
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1811758
Title:
virtio-rng backend should use getentropy() syscall when available
Status in QEMU:
New
Bug description:
According to https://wiki.qemu.org/Features/VirtIORNG the default
backend for `virtio-rng-pci` is `/dev/random`. Alternately, the user
can point it to a different backend file, like `/dev/urandom`.
However, both of these files have suboptimal behavior in one way or
another, as documented in `random(7)`. Instead, the default behavior
should be to pull the requested octets from the `getrandom()` system
call, if available, called with no flags set.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1811758/+subscriptions
next prev parent reply other threads:[~2019-04-16 5:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 6:47 [Qemu-devel] [Bug 1811758] [NEW] virtio-rng backend should use getentropy() syscall when available dkg
2019-01-15 6:49 ` [Qemu-devel] [Bug 1811758] " dkg
2019-04-16 2:16 ` dkg
2019-04-16 2:16 ` dkg
2019-04-16 5:37 ` Thomas Huth [this message]
2019-04-16 5:37 ` Thomas Huth
2019-04-17 16:54 ` Amit Shah
2019-04-17 16:54 ` Amit Shah
2019-11-13 9:34 ` Laurent Vivier
2020-01-09 13:45 ` Thomas Huth
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=155539304622.13876.14766283166073144058.malone@gac.canonical.com \
--to=1811758@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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).