From: Eric Blake <eblake@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Use qemu_open / qemu_close in rng backend
Date: Fri, 01 Mar 2013 06:36:00 -0700 [thread overview]
Message-ID: <5130AEC0.5060800@redhat.com> (raw)
In-Reply-To: <5130A4E3.70003@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
[don't you also need to cc the main qemu list, even for trivial patches?]
On 03/01/2013 05:53 AM, Stefan Berger wrote:
> In the rng backend use qemu_open and qemu_close rather than POSIX
> open/close.
>
> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
>
> diff --git a/backends/rng-random.c b/backends/rng-random.c
> index 0d11088..acd20af 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 = open(s->filename, O_RDONLY | O_NONBLOCK);
> + s->fd = qemu_open(s->filename, O_RDONLY | O_NONBLOCK);
>
> if (s->fd == -1) {
> error_set(errp, QERR_OPEN_FILE_FAILED, s->filename);
> @@ -130,7 +130,7 @@ static void rng_random_finalize(Object *obj)
> qemu_set_fd_handler(s->fd, NULL, NULL, NULL);
>
> if (s->fd != -1) {
> - close(s->fd);
> + qemu_close(s->fd);
> }
>
> g_free(s->filename);
>
>
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
parent reply other threads:[~2013-03-01 13:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5130A4E3.70003@linux.vnet.ibm.com>]
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=5130AEC0.5060800@redhat.com \
--to=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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).