From: Vivek Goyal <vgoyal@redhat.com>
To: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>
Cc: virtio-fs@redhat.com
Subject: Re: [Virtio-fs] [PATCH v3 0/2] Fix xattr operation
Date: Fri, 21 Feb 2020 10:18:35 -0500 [thread overview]
Message-ID: <20200221151835.GB25974@redhat.com> (raw)
In-Reply-To: <20200220114704.11592-1-misono.tomohiro@jp.fujitsu.com>
On Thu, Feb 20, 2020 at 08:47:02PM +0900, Misono Tomohiro wrote:
> This fixes the xattr operation for directory and special files
> (which can be tested by xfstests generic/062 with -o xattr option).
>
> The overall logic is switched back to the same as v1 in favor of performance
> (i.e. keep original implementation for regular files/directories)
> but I add a cleanup patch to improve readability as requested by Vivek.
>
> Known issue is that if xattr enabled, seek sanity tests (generic/285,
> 436) will fail. However, I understand this is not a very serious bug
> like data corruption so leave it for now.
Hi Misono,
Do you know why generic/285 and generic/436 fail with xattr enabled. Is
it something easily fixable later.
>
> One question; I remove error handling of fchdir() in v3 since
> I believe fchdir to proc_self_fd/root.fd cannot fail in the situation
> but should I add error handling?
I would think its good to have error handling for fchdir() case. We don't
expect it, but if something goes wrong, we will like to catch it.
Thanks
Vivek
>
> change v2 -> v3:
> - rebased to current dev branch
> - add cleanup path (first one) to simplify main patch (second patch)
> - restore the logic of v1 in favor of performance
> (as a result seek sanity test failure is not fixed by this series)
> - remove error handling of fchdir
> - drop ACL fix included in v2 for now to focus xattr
>
> v2 patch: https://www.redhat.com/archives/virtio-fs/2020-January/msg00131.html
>
> Thanks!
>
> Misono Tomohiro (2):
> virtiofs: passthrough_ll: cleanup getxattr/listxattr
> virtiofs: Fix xattr operations
>
> tools/virtiofsd/fuse_virtio.c | 13 +++
> tools/virtiofsd/passthrough_ll.c | 141 +++++++++++++++----------------
> tools/virtiofsd/seccomp.c | 6 ++
> 3 files changed, 87 insertions(+), 73 deletions(-)
>
> --
> 2.21.1
>
next prev parent reply other threads:[~2020-02-21 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 11:47 [Virtio-fs] [PATCH v3 0/2] Fix xattr operation Misono Tomohiro
2020-02-20 11:47 ` [Virtio-fs] [PATCH v3 1/2] virtiofs: passthrough_ll: cleanup getxattr/listxattr Misono Tomohiro
2020-02-21 15:49 ` Vivek Goyal
2020-02-20 11:47 ` [Virtio-fs] [PATCH v3 2/2] virtiofs: Fix xattr operations Misono Tomohiro
2020-02-21 16:20 ` Vivek Goyal
2020-02-21 15:18 ` Vivek Goyal [this message]
2020-02-27 5:16 ` [Virtio-fs] [PATCH v3 0/2] Fix xattr operation misono.tomohiro
2020-02-28 13:00 ` Vivek Goyal
2020-02-21 18:50 ` Vivek Goyal
2020-02-27 5:20 ` misono.tomohiro
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=20200221151835.GB25974@redhat.com \
--to=vgoyal@redhat.com \
--cc=misono.tomohiro@jp.fujitsu.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.