From: Lei Li <lilei@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, mohan@in.ibm.com, Lei Li <lilei@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 3/6] net/tap: replace recv_fd with qemu_recv_with_fd
Date: Wed, 8 Jan 2014 17:12:53 +0800 [thread overview]
Message-ID: <1389172376-30636-4-git-send-email-lilei@linux.vnet.ibm.com> (raw)
In-Reply-To: <1389172376-30636-1-git-send-email-lilei@linux.vnet.ibm.com>
Signed-off-by: Lei Li <lilei@linux.vnet.ibm.com>
---
net/tap.c | 40 +++-------------------------------------
1 files changed, 3 insertions(+), 37 deletions(-)
diff --git a/net/tap.c b/net/tap.c
index 39c1cda..97ee2e8 100644
--- a/net/tap.c
+++ b/net/tap.c
@@ -39,6 +39,7 @@
#include "sysemu/sysemu.h"
#include "qemu-common.h"
#include "qemu/error-report.h"
+#include "qemu/fd-exchange.h"
#include "net/tap.h"
@@ -385,40 +386,6 @@ static int launch_script(const char *setup_script, const char *ifname, int fd)
return -1;
}
-static int recv_fd(int c)
-{
- int fd;
- uint8_t msgbuf[CMSG_SPACE(sizeof(fd))];
- struct msghdr msg = {
- .msg_control = msgbuf,
- .msg_controllen = sizeof(msgbuf),
- };
- struct cmsghdr *cmsg;
- struct iovec iov;
- uint8_t req[1];
- ssize_t len;
-
- cmsg = CMSG_FIRSTHDR(&msg);
- cmsg->cmsg_level = SOL_SOCKET;
- cmsg->cmsg_type = SCM_RIGHTS;
- cmsg->cmsg_len = CMSG_LEN(sizeof(fd));
- msg.msg_controllen = cmsg->cmsg_len;
-
- iov.iov_base = req;
- iov.iov_len = sizeof(req);
-
- msg.msg_iov = &iov;
- msg.msg_iovlen = 1;
-
- len = recvmsg(c, &msg, 0);
- if (len > 0) {
- memcpy(&fd, CMSG_DATA(cmsg), sizeof(fd));
- return fd;
- }
-
- return len;
-}
-
static int net_bridge_run_helper(const char *helper, const char *bridge)
{
sigset_t oldmask, mask;
@@ -489,12 +456,11 @@ static int net_bridge_run_helper(const char *helper, const char *bridge)
} else if (pid > 0) {
int fd;
+ char req[1] = { 0x00 };
close(sv[1]);
- do {
- fd = recv_fd(sv[0]);
- } while (fd == -1 && errno == EINTR);
+ qemu_recv_with_fd(sv[0], &fd, &req, sizeof(req));
close(sv[0]);
--
1.7.7.6
next prev parent reply other threads:[~2014-01-08 9:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 9:12 [Qemu-devel] [PATCH resend 0/6 RFC] Provide common methods for exchange FD Lei Li
2014-01-08 9:12 ` [Qemu-devel] [PATCH 1/6] qemu-fd-exchange: provide common methods for exchange fd Lei Li
2014-01-16 15:16 ` Eric Blake
2014-01-17 3:40 ` Lei Li
2014-01-16 15:26 ` Eric Blake
2014-01-17 3:41 ` Lei Li
2014-01-17 10:02 ` Daniel P. Berrange
2014-01-20 1:50 ` Lei Li
2014-01-08 9:12 ` [Qemu-devel] [PATCH 2/6] qemu-bridge-helper: replace send_fd with qemu_send_with_fd Lei Li
2014-01-08 9:12 ` Lei Li [this message]
2014-01-08 9:12 ` [Qemu-devel] [PATCH 4/6] virtfs-proxy-helper: " Lei Li
2014-01-16 10:15 ` Daniel P. Berrange
2014-01-17 3:40 ` Lei Li
2014-01-08 9:12 ` [Qemu-devel] [PATCH 5/6] virtio-9p-proxy: replace v9fs_receivefd with qemu_recv_with_fd Lei Li
2014-01-16 10:16 ` Daniel P. Berrange
2014-01-17 3:40 ` Lei Li
2014-01-08 9:12 ` [Qemu-devel] [PATCH 6/6] migration-local: replace send_pipefd with qemu_send_with_fd Lei Li
2014-01-16 9:26 ` [Qemu-devel] [PATCH resend 0/6 RFC] Provide common methods for exchange FD Lei Li
2014-01-16 10:17 ` Daniel P. Berrange
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=1389172376-30636-4-git-send-email-lilei@linux.vnet.ibm.com \
--to=lilei@linux.vnet.ibm.com \
--cc=mohan@in.ibm.com \
--cc=pbonzini@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).