From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, aliguori@us.ibm.com,
stefanha@linux.vnet.ibm.com, libvir-list@redhat.com,
lcapitulino@redhat.com, eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 1/6] qemu-char: Add MSG_CMSG_CLOEXEC flag to recvmsg
Date: Fri, 03 Aug 2012 13:33:25 -0400 [thread overview]
Message-ID: <501C0B65.2090409@linux.vnet.ibm.com> (raw)
In-Reply-To: <1344014889-12390-2-git-send-email-coreyb@linux.vnet.ibm.com>
If these patches are acceptable, I'll resend and get the version history
out of the commit message.
--
Regards,
Corey
On 08/03/2012 01:28 PM, Corey Bryant wrote:
> Set the close-on-exec flag for the file descriptor received
> via SCM_RIGHTS.
>
> v4
> -This patch is new in v4 (eblake@redhat.com)
>
> v5
> -Fallback to FD_CLOEXEC if MSG_CMSG_CLOEXEC is not available
> (eblake@redhat.com, stefanha@linux.vnet.ibm.com)
>
> v6
> -Set cloexec on correct fd (eblake@redhat.com)
>
> Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
> ---
> qemu-char.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index c2aaaee..ab4a928 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -2238,6 +2238,9 @@ static void unix_process_msgfd(CharDriverState *chr, struct msghdr *msg)
> if (fd < 0)
> continue;
>
> +#ifndef MSG_CMSG_CLOEXEC
> + qemu_set_cloexec(fd);
> +#endif
> if (s->msgfd != -1)
> close(s->msgfd);
> s->msgfd = fd;
> @@ -2253,6 +2256,7 @@ static ssize_t tcp_chr_recv(CharDriverState *chr, char *buf, size_t len)
> struct cmsghdr cmsg;
> char control[CMSG_SPACE(sizeof(int))];
> } msg_control;
> + int flags = 0;
> ssize_t ret;
>
> iov[0].iov_base = buf;
> @@ -2263,9 +2267,13 @@ static ssize_t tcp_chr_recv(CharDriverState *chr, char *buf, size_t len)
> msg.msg_control = &msg_control;
> msg.msg_controllen = sizeof(msg_control);
>
> - ret = recvmsg(s->fd, &msg, 0);
> - if (ret > 0 && s->is_unix)
> +#ifdef MSG_CMSG_CLOEXEC
> + flags |= MSG_CMSG_CLOEXEC;
> +#endif
> + ret = recvmsg(s->fd, &msg, flags);
> + if (ret > 0 && s->is_unix) {
> unix_process_msgfd(chr, &msg);
> + }
>
> return ret;
> }
>
next prev parent reply other threads:[~2012-08-03 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 17:28 [Qemu-devel] [PATCH v6 0/6] file descriptor passing using fd sets Corey Bryant
2012-08-03 17:28 ` [Qemu-devel] [PATCH v6 1/6] qemu-char: Add MSG_CMSG_CLOEXEC flag to recvmsg Corey Bryant
2012-08-03 17:33 ` Corey Bryant [this message]
2012-08-03 17:28 ` [Qemu-devel] [PATCH v6 2/6] qapi: Introduce add-fd, remove-fd, query-fdsets Corey Bryant
2012-08-07 18:16 ` Stefan Hajnoczi
2012-08-07 19:59 ` Corey Bryant
2012-08-08 8:52 ` Stefan Hajnoczi
2012-08-08 13:40 ` Corey Bryant
2012-08-03 17:28 ` [Qemu-devel] [PATCH v6 3/6] monitor: Clean up fd sets on monitor disconnect Corey Bryant
2012-08-07 17:32 ` Stefan Hajnoczi
2012-08-07 19:36 ` Corey Bryant
2012-08-03 17:28 ` [Qemu-devel] [PATCH v6 4/6] block: Convert open calls to qemu_open Corey Bryant
2012-08-03 17:28 ` [Qemu-devel] [PATCH v6 5/6] block: Convert close calls to qemu_close Corey Bryant
2012-08-03 17:28 ` [Qemu-devel] [PATCH v6 6/6] block: Enable qemu_open/close to work with fd sets Corey Bryant
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=501C0B65.2090409@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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.