From: Eryu Guan <guaneryu@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Ronnie Sahlberg <lsahlber@redhat.com>, fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] cifs: add test that setfattr -x fails non-existing EAs
Date: Thu, 14 Feb 2019 13:50:55 +0800 [thread overview]
Message-ID: <20190214055055.GX2713@desktop> (raw)
In-Reply-To: <CAOQ4uxgEkG2hHXcLrc5mB0k5h9kw_QNSw-vJcABt0o7+qccvcA@mail.gmail.com>
On Mon, Feb 11, 2019 at 09:15:28AM +0200, Amir Goldstein wrote:
> Hi Ronnie,
>
> CC the correct list <fstests@vger.kernel.org>
>
> On Mon, Feb 11, 2019 at 7:21 AM Ronnie Sahlberg <lsahlber@redhat.com> wrote:
> >
> > We just fixed a bug in cifs.ko where it would incorrectly return success
> > for setfattr -x user.does-not-exist.
> >
> > This patch adds a test case for this.
> >
> > Xfstests already have tests for setfattr -x in generic/097
> > but we can not yet use that test for cifs since we can only support
> > the user namespace.
>
> Mmm... that's not a reason to write a cifs specific test.
> 1. Your test is not cifs specific so should be generic
> 2. There is a lot of other test coverage cifs is missing from generic/097
>
> What I suggest is:
> - implement _require_trusted_attrs
> - replace _require_attrs with _require_trusted_attrs in the few
> generic tests that use trusted xattrs
> - I counted 5 generic tests and there is also generic/079 that
> sets trusted xattr via t_immutable and doesn't currently _require_attrs
> at all. Frankly, it looks like most of those test could use user.* xattrs,
> but whatever.
> - Anyway, please stay away from the overlay trusted xattr tests.
> - clone generic/097 to a new test that only _require_attrs
> leaving out the trusted xattrs
Yeah, these suggestions all look good to me,
>
> After that change, cifs will not fail on the trusted xattr tests
> and instead those tests will be properly skipped for cifs.
and this would be the ideal situation for cifs :)
Thanks,
Eryu
next prev parent reply other threads:[~2019-02-14 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190211051932.20542-1-lsahlber@redhat.com>
[not found] ` <20190211051932.20542-2-lsahlber@redhat.com>
2019-02-11 7:15 ` [PATCH] cifs: add test that setfattr -x fails non-existing EAs Amir Goldstein
2019-02-14 5:50 ` Eryu Guan [this message]
2019-02-11 21:51 ` Dave Chinner
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=20190214055055.GX2713@desktop \
--to=guaneryu@gmail.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=lsahlber@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