From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] rng backend: open backend in blocking mode
Date: Mon, 01 Apr 2013 09:02:46 -0500 [thread overview]
Message-ID: <87eheus60p.fsf@codemonkey.ws> (raw)
In-Reply-To: <74d06e1f94cc2337aa1bb6784a7ad2210ec55364.1364808312.git.amit.shah@redhat.com>
Amit Shah <amit.shah@redhat.com> writes:
> Opening backends in non-blocking mode isn't necessary, we don't do
> anything while waiting for data.
>
> This also excuses us from checking for EAGAIN, which for the default
> random backend, is a very common return error type.
It's not common... It really shouldn't happen however.
> Starting the guest
> with '-device virtio-rng-pci', issuing a 'cat /dev/hwrng' in the guest
> while also doing 'cat /dev/random' on the host causes
You are essentially cat'ing the same device twice. What's happening is
that there is entropy available in /dev/random so a select()
notification happens but before we are able to read() it, the cat of
/dev/hwrng ends up consuming that entropy.
This would never happen with a socket, for instance. /dev/random is
special in there are multiple readers.
>
> backends/rng-random.c:44:entropy_available: assertion failed: (len != -1)
>
> without this fix.
This fix would cause QEMU to block indefinitely which I don't think is
very good behavior. I think a better solution would be:
diff --git a/backends/rng-random.c b/backends/rng-random.c
index acd20af..9fde566 100644
--- a/backends/rng-random.c
+++ b/backends/rng-random.c
@@ -41,6 +41,9 @@ static void entropy_available(void *opaque)
ssize_t len;
len = read(s->fd, buffer, s->size);
+ if (len == -1 && errno == EINTR) {
+ return;
+ }
g_assert(len != -1);
s->receive_func(s->opaque, buffer, len);
Since this simply ignores the extraneous select notification that occurs
because of the race above.
Regards,
Anthony Liguori
>
> Reported-by: yunpingzheng <yunzheng@redhat.com>
> Signed-off-by: Amit Shah <amit.shah@redhat.com>
> ---
> backends/rng-random.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/backends/rng-random.c b/backends/rng-random.c
> index acd20af..252139b 100644
> --- a/backends/rng-random.c
> +++ b/backends/rng-random.c
> @@ -74,7 +74,7 @@ static void rng_random_opened(RngBackend *b, Error **errp)
> error_set(errp, QERR_INVALID_PARAMETER_VALUE,
> "filename", "a valid filename");
> } else {
> - s->fd = qemu_open(s->filename, O_RDONLY | O_NONBLOCK);
> + s->fd = qemu_open(s->filename, O_RDONLY);
>
> if (s->fd == -1) {
> error_set(errp, QERR_OPEN_FILE_FAILED, s->filename);
> --
> 1.8.1.4
next prev parent reply other threads:[~2013-04-01 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 9:25 [Qemu-devel] [PATCH 1/1] rng backend: open backend in blocking mode Amit Shah
2013-04-01 14:02 ` Anthony Liguori [this message]
2013-04-02 10:35 ` Amit Shah
2013-04-02 12:52 ` Anthony Liguori
2013-04-03 6:28 ` Amit Shah
2013-04-03 20:08 ` Anthony Liguori
2013-04-08 6:09 ` Amit Shah
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=87eheus60p.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=amit.shah@redhat.com \
--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).