From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Steve French <smfrench@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: generic: test statx attribute_mask setting
Date: Thu, 25 Apr 2019 14:10:07 -0700 [thread overview]
Message-ID: <20190425211007.GA755788@magnolia> (raw)
In-Reply-To: <CAH2r5mu9WFqz=15ENbt27wW+qP+XaJgyGs-B8Yq4_sn931vxnA@mail.gmail.com>
On Thu, Apr 25, 2019 at 01:39:40PM -0700, Steve French wrote:
> I noticed that the patch "generic: test statx attribute_mask setting"
> seems to cause a failure on xfstest 532. I am trying with current
> xfsprogs and xfstests from git.kernel.org git trees for those. The
> output is:
>
> (generic/532 [not run] xfs_io statx command does not support attributes_mask)
>
> due to this line:
>
> 0ff18d367 (Darrick J. Wong 2019-03-04 13:19:35 -0800 35) get_attributes_mask() {
> 0ff18d367 (Darrick J. Wong 2019-03-04 13:19:35 -0800 36)
> $XFS_IO_PROG -r -c "statx -r" $1 | grep 'stat.attributes_mask =' | cut
> -d ' ' -f 3
>
> But attributes_mask is not returned by current xfsprogs (instead it
> appears to be "mask"
That's stx_mask, which are the STATX_* flags.
> not "attributes_mask"). If you grep xfsprogs for "attributes_mask" -
> there are no hits.
>
> Is this a typo in line 36 of tests/generic/532 where it is searching
> for "stat.attributes_mask" not "stat.mask"?
Nope, stx_attributes_mask is a "new" field that shows which
stx_attributes flags (STATX_ATTR_*) are known to the filesystem. It's
not really new (it showed up in 4.11 along with the rest of statx) but
I only seemed to notice its existence recently. Support for this new
field will appear in xfsprogs 5.0.
--D
> --
> Thanks,
>
> Steve
next prev parent reply other threads:[~2019-04-25 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 20:39 generic: test statx attribute_mask setting Steve French
2019-04-25 21:10 ` Darrick J. Wong [this message]
2019-04-25 21:42 ` Steve French
2019-04-26 3:50 ` Darrick J. Wong
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=20190425211007.GA755788@magnolia \
--to=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=smfrench@gmail.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