From: Vivek Goyal <vgoyal@redhat.com>
To: Fotis Xenakis <foxen@windowslive.com>
Cc: "virtio-fs@redhat.com" <virtio-fs@redhat.com>
Subject: Re: [Virtio-fs] [PATCH] Fix file descriptor passed for setupmapping
Date: Mon, 18 May 2020 08:37:37 -0400 [thread overview]
Message-ID: <20200518123737.GA268933@redhat.com> (raw)
In-Reply-To: <VI1PR03MB4383EAFC7403141AB2278802A6BD0@VI1PR03MB4383.eurprd03.prod.outlook.com>
On Fri, May 15, 2020 at 04:50:31PM +0000, Fotis Xenakis wrote:
> From: Liu Bo <bo.liu@linux.alibaba.com>
> Sent: Friday, May 15, 2020 06:48
> To: Fotis Xenakis <foxen@windowslive.com>
> Cc: virtio-fs@redhat.com <virtio-fs@redhat.com>
> Subject: Re: [Virtio-fs] [PATCH] Fix file descriptor passed for setupmapping
>
> On Wed, May 13, 2020 at 07:33:56PM +0300, Fotis Xenakis wrote:
> > Currently, during FUSE_SETUPMAPPING, virtiofsd passes the wrong file
> > descriptor for the file to mmap() to QEMU (specifically, it passes the
> > file handle as requested from the guest).
> >
> > This fixes it, using lo_fi_fd() to map the file handle to the right file
> > descriptor on the host.
> >
>
> Looks good, guest has been setting fi as NULL though.
> As far as I can see, this function is only called from [1], which passes fi as NULL only when the file handle passed from the guest is (uint64_t)-1. In my testing this was never the case though.
Hi Fotis,
Do you know what's different about your setup. This has been working for
me so clearly I am seeing fi as NULL.
Vivek
next prev parent reply other threads:[~2020-05-18 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 16:33 [Virtio-fs] [PATCH] Fix file descriptor passed for setupmapping Fotis Xenakis
2020-05-15 3:48 ` Liu Bo
2020-05-15 16:50 ` Fotis Xenakis
2020-05-18 12:37 ` Vivek Goyal [this message]
2020-05-18 21:17 ` Fotis Xenakis
2020-05-15 12:52 ` Vivek Goyal
2020-05-18 10:45 ` Dr. David Alan Gilbert
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=20200518123737.GA268933@redhat.com \
--to=vgoyal@redhat.com \
--cc=foxen@windowslive.com \
--cc=virtio-fs@redhat.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.