From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Xiong Zhou <xzhou@redhat.com>, fstests <fstests@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [xfstests v4 6/8] overlay: can not change underlying immutable file
Date: Wed, 5 Apr 2017 10:50:26 +0800 [thread overview]
Message-ID: <20170405025026.GT22845@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAOQ4uxgv4gzfn6SphscYsBOd3G4xq4TVMnCEZfpcxqox2uUYNg@mail.gmail.com>
[Sorry for the late response, was in public holiday]
On Tue, Apr 04, 2017 at 07:31:46PM +0300, Amir Goldstein wrote:
> On Tue, Apr 4, 2017 at 2:19 PM, Amir Goldstein <amir73il@gmail.com> wrote:
> > On Thu, Feb 23, 2017 at 11:42 AM, Xiong Zhou <xzhou@redhat.com> wrote:
> [...]
> >> +
> >> +# Modify as appropriate.
> >> +_supported_fs overlay
> >> +_supported_os Linux
> >> +_require_scratch
> >> +_require_chattr
> >> +
> >
> > Eryu,
> >
> > A way-post-merge bug spotting:
> > Should be "_require_chattr i".
> > _require_chattr alone makes no sense (and should probably be reported
> > as an error)
> >
> > I may get to send a fix, but not too soon..
> >
>
> Apparently, _require_chattr with no arguments does do what it is expected to do,
> or as David wrote in the new documentation patch:
> "The test requires that the chattr command be available and supported by
> the $TEST_DEV filesystem"
>
> But it appears to be doing the right thing by coincidence??
> Without any arguments to _require_chattr, it ends up executing
>
> chattr + $file
>
> and
>
> chattr - file
>
> The former, surprisingly does do FS_IOC_GETFLAGS and FS_IOC_SETFLAGS
> on the file, so the check is correct.
>
> The latter spews this error into full output "Must use '-v', =, - or +"
> and ignored the failure - again correct, but seems unintentional.
>
> I wonder if we should forbid the use of _require_chattr with no args?
I agreed. Do you mind sending a fix?
> It's only user right now is test overlay/027 and that seems like a bug
> (test should _require_chattr i).
Agreed. Xiong has acknowledged the bug, hopefully he will send a fix.
Thanks for finding this!
Eryu
next prev parent reply other threads:[~2017-04-05 2:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 9:42 [xfstests v4 0/8] bunch of overlay tests Xiong Zhou
2017-02-23 9:42 ` [xfstests v4 1/8] overlay: disallow overlayfs as upperdir Xiong Zhou
2017-02-23 9:42 ` [xfstests v4 2/8] overlay: work dir in overlay inherits no ACLs Xiong Zhou
2017-02-23 10:44 ` Eryu Guan
2017-02-23 9:42 ` [xfstests v4 3/8] overlay: test workdir cleanup in mounting Xiong Zhou
2017-02-23 9:42 ` [xfstests v4 4/8] overlay: permission check with cached acls in tmpfs Xiong Zhou
2017-02-23 10:52 ` Eryu Guan
2017-02-23 12:49 ` Xiong Zhou
2017-02-23 9:42 ` [xfstests v4 5/8] overlay: filter out xattr starts with "trusted.overlay." Xiong Zhou
2017-02-23 9:42 ` [xfstests v4 6/8] overlay: can not change underlying immutable file Xiong Zhou
2017-04-04 11:19 ` Amir Goldstein
2017-04-04 16:31 ` Amir Goldstein
2017-04-05 2:25 ` Xiong Zhou
2017-04-05 2:50 ` Eryu Guan [this message]
2017-04-05 10:52 ` Amir Goldstein
2017-02-23 9:42 ` [xfstests v4 7/8] overlay: test flock after copied up Xiong Zhou
2017-02-23 9:42 ` [xfstests v4 8/8] overlay: accessing stacked overlayfs files Xiong Zhou
2017-03-03 8:19 ` Amir Goldstein
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=20170405025026.GT22845@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=amir73il@gmail.com \
--cc=dhowells@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=xzhou@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