From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] osdep: Introduce qemu_dup
Date: Wed, 22 Jun 2016 09:21:12 -0600 [thread overview]
Message-ID: <576AACE8.5090506@redhat.com> (raw)
In-Reply-To: <20160622125320.31279-2-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On 06/22/2016 06:53 AM, Fam Zheng wrote:
> And use it in qemu_dup_flags.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> include/qemu/osdep.h | 3 +++
> util/osdep.c | 23 +++++++++++++++--------
> 2 files changed, 18 insertions(+), 8 deletions(-)
>
> +int qemu_dup(int fd)
> +{
> + int ret;
> +#ifdef F_DUPFD_CLOEXEC
> + ret = fcntl(fd, F_DUPFD_CLOEXEC, 0);
> +#else
> + ret = dup(fd);
> + if (ret != -1) {
> + qemu_set_cloexec(ret);
> + }
Is it any more efficient to try and use dup3(fd, 0, O_CLOEXEC), or are
we assuming that F_DUPFD_CLOEXEC and dup3() are only likely to both be
present or absent?
Otherwise,
Reviewed-by: Eric Blake <eblake@redhat.com>
--
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: 604 bytes --]
next prev parent reply other threads:[~2016-06-22 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 12:53 [Qemu-devel] [PATCH v2 0/2] block: Add qemu_dup in osdep.c and use it Fam Zheng
2016-06-22 12:53 ` [Qemu-devel] [PATCH v2 1/2] osdep: Introduce qemu_dup Fam Zheng
2016-06-22 15:21 ` Eric Blake [this message]
2016-06-22 15:24 ` Eric Blake
2016-06-22 12:53 ` [Qemu-devel] [PATCH v2 2/2] raw-posix: Use qemu_dup Fam Zheng
2016-07-07 21:14 ` [Qemu-devel] [Qemu-block] [PATCH v2 0/2] block: Add qemu_dup in osdep.c and use it John Snow
2016-07-08 10:17 ` Kevin Wolf
-- strict thread matches above, loose matches on Subject: below --
2016-06-22 13:32 [Qemu-devel] " Fam Zheng
2016-06-22 13:32 ` [Qemu-devel] [PATCH v2 1/2] osdep: Introduce qemu_dup Fam Zheng
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=576AACE8.5090506@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).