From: "Daniel P. Berrange" <berrange@redhat.com>
To: Lei Li <lilei@linux.vnet.ibm.com>
Cc: pbonzini@redhat.com, mohan@in.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/6] virtfs-proxy-helper: replace send_fd with qemu_send_with_fd
Date: Thu, 16 Jan 2014 10:15:22 +0000 [thread overview]
Message-ID: <20140116101522.GB29231@redhat.com> (raw)
In-Reply-To: <1389172376-30636-5-git-send-email-lilei@linux.vnet.ibm.com>
On Wed, Jan 08, 2014 at 05:12:54PM +0800, Lei Li wrote:
> Signed-off-by: Lei Li <lilei@linux.vnet.ibm.com>
> ---
> fsdev/virtfs-proxy-helper.c | 51 ++++++------------------------------------
> hw/9pfs/virtio-9p-proxy.h | 5 ----
> 2 files changed, 8 insertions(+), 48 deletions(-)
>
> diff --git a/fsdev/virtfs-proxy-helper.c b/fsdev/virtfs-proxy-helper.c
> index 713a7b2..44c6e61 100644
> --- a/fsdev/virtfs-proxy-helper.c
> +++ b/fsdev/virtfs-proxy-helper.c
> -static int send_fd(int sockfd, int fd)
> -{
...
> - /* No ancillary data on error */
> - if (fd < 0) {
> - /* fd is really negative errno if the request failed */
> - data = fd;
> - } else {
> - data = V9FS_FD_VALID;
The way data is initialized here...
> @@ -784,11 +743,17 @@ static void usage(char *prog)
> static int process_reply(int sock, int type,
> struct iovec *out_iovec, int retval)
> {
> + int data = V9FS_FD_VALID;
Doesn't match what you do here.
> +
> switch (type) {
> case T_OPEN:
> case T_CREATE:
> - if (send_fd(sock, retval) < 0) {
> + if (qemu_send_with_fd(sock, retval, &data, sizeof(data)) < 0) {
> return -1;
> + } else {
> + if (retval >= 0) {
> + close(retval);
> + }
> }
> break;
> case T_MKNOD:
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2014-01-16 10:15 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 ` [Qemu-devel] [PATCH 3/6] net/tap: replace recv_fd with qemu_recv_with_fd Lei Li
2014-01-08 9:12 ` [Qemu-devel] [PATCH 4/6] virtfs-proxy-helper: replace send_fd with qemu_send_with_fd Lei Li
2014-01-16 10:15 ` Daniel P. Berrange [this message]
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=20140116101522.GB29231@redhat.com \
--to=berrange@redhat.com \
--cc=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).