From: Xiaoli Feng <xifeng@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: fstests@vger.kernel.org, smfrench@gmail.com,
Ronnie Sahlberg <lsahlber@redhat.com>,
sprabhu <sprabhu@redhat.co>,
linux-cifs@vger.kernel.org
Subject: Re: [PATCH v1] xfstests: filter the default EA
Date: Wed, 19 Dec 2018 21:17:02 -0500 (EST) [thread overview]
Message-ID: <966737066.61401666.1545272222334.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20181219071834.GA14993@infradead.org>
Hi Christoph,
----- Original Message -----
> From: "Christoph Hellwig" <hch@infradead.org>
> To: "XiaoLi Feng" <xifeng@redhat.com>
> Cc: fstests@vger.kernel.org
> Sent: Wednesday, December 19, 2018 3:18:34 PM
> Subject: Re: [PATCH v1] xfstests: filter the default EA
>
> On Wed, Dec 19, 2018 at 11:44:28AM +0800, XiaoLi Feng wrote:
> > From: xiaoli feng <xifeng@redhat.com>
> >
> > For some filesystems, such as CIFS, the file or directory has the
> > default extend attribute. It makes these tests generic/020
> > generic/337 generic/377 failed. Now add this patch to filter the
> > default EA.
>
> What is "the default EA"? This sounds like a CIFS bug to me.
the default EA means the new file or directory has extended attributes.
# touch cifs/file
# getfattr cifs/file
# file: cifs/file
user.security.selinux
I don't think it's a CIFS bug to me. But we need the CIFS developers's
analysis. cc the cifs developer mail.
Thanks.
>
next prev parent reply other threads:[~2018-12-20 2:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 3:44 [PATCH v1] xfstests: filter the default EA XiaoLi Feng
2018-12-19 7:18 ` Christoph Hellwig
2018-12-20 2:17 ` Xiaoli Feng [this message]
2018-12-20 2:24 ` Steve French
2018-12-20 3:03 ` Xiaoli Feng
2018-12-20 3:53 ` Steve French
2018-12-20 5:23 ` Xiaoli Feng
2018-12-20 5:37 ` Steve French
2018-12-21 4:01 ` Xiaoli Feng
2018-12-21 4:14 ` Steve French
2018-12-20 7:41 ` Christoph Hellwig
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=966737066.61401666.1545272222334.JavaMail.zimbra@redhat.com \
--to=xifeng@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=smfrench@gmail.com \
--cc=sprabhu@redhat.co \
/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