From: Vivek Goyal <vgoyal@redhat.com>
To: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>
Cc: virtio-fs@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v4 0/2] virtiofsd: Fix xattr operations
Date: Fri, 28 Feb 2020 07:50:44 -0500 [thread overview]
Message-ID: <20200228125044.GA21565@redhat.com> (raw)
In-Reply-To: <20200227055927.24566-1-misono.tomohiro@jp.fujitsu.com>
On Thu, Feb 27, 2020 at 02:59:25PM +0900, Misono Tomohiro wrote:
> Currently xattr operations on virtiofs does not work properly in some case:
> - directory ... cannot set
> - special files (pipe) ... cause hang
>
> This fixes these problems and now xfstests generic/062 passes on virtiofs
> with -o xattr option (I tested with xfs).
>
> v3 -> v4:
> - No logic change
> - Some code style fix/update comments and commit log as suggested by Vivek
> - CC qemu-devel ML too
>
> Previous versions can be found in virtiofs ML:
> v3: https://www.redhat.com/archives/virtio-fs/2020-February/msg00032.html
>
> Thanks,
> Misono Tomohiro (2):
> virtiofsd: passthrough_ll: cleanup getxattr/listxattr
> virtiofsd: Fix xattr operations
Thanks Misono for this work. I am fine with this patch series.
Acked-by: Vivek Goyal <vgoyal@redhat.com>
Thanks
Vivek
>
> tools/virtiofsd/fuse_virtio.c | 13 +++
> tools/virtiofsd/passthrough_ll.c | 139 ++++++++++++++++---------------
> tools/virtiofsd/seccomp.c | 6 ++
> 3 files changed, 89 insertions(+), 69 deletions(-)
>
> --
> 2.21.1
>
next prev parent reply other threads:[~2020-02-28 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 5:59 [PATCH v4 0/2] virtiofsd: Fix xattr operations Misono Tomohiro
2020-02-27 5:59 ` [PATCH v4 1/2] virtiofsd: passthrough_ll: cleanup getxattr/listxattr Misono Tomohiro
2020-02-27 5:59 ` [PATCH v4 2/2] virtiofsd: Fix xattr operations Misono Tomohiro
2020-02-28 12:50 ` Vivek Goyal [this message]
2020-03-03 11:37 ` [Virtio-fs] [PATCH v4 0/2] " 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=20200228125044.GA21565@redhat.com \
--to=vgoyal@redhat.com \
--cc=misono.tomohiro@jp.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--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 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).