From: Eryu Guan <guaneryu@gmail.com>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 3/3] generic: exclude selinux xattr form being considered
Date: Wed, 28 Nov 2018 12:37:05 +0800 [thread overview]
Message-ID: <20181128043705.GS3889@desktop> (raw)
In-Reply-To: <20181127214308.137410-4-gwendal@chromium.org>
On Tue, Nov 27, 2018 at 01:43:08PM -0800, Gwendal Grignou wrote:
> Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
I didn't see such failures before, could you please provide more info in
the commit log about the problem? So I can try to reproduce the failure.
> ---
> common/filter | 1 +
> tests/generic/062 | 2 +-
> tests/generic/377 | 2 +-
> 3 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/common/filter b/common/filter
> index ed082d24..3ca40431 100644
> --- a/common/filter
> +++ b/common/filter
> @@ -290,6 +290,7 @@ _filter_scratch()
> # so substitute SCRATCH_MNT first
> sed -e "s,\B$SCRATCH_MNT,SCRATCH_MNT,g" \
> -e "s,\B$SCRATCH_DEV,SCRATCH_DEV,g" \
> + -e "/security\.selinux/d" \
> -e "/.use_space/d"
This doesn't belong to _filter_scratch but to filters that filter xattr.
I want to understand & reproduce the problem so I know where the failure
comes from and think about what the best fix would be.
Thanks,
Eryu
> }
>
> diff --git a/tests/generic/062 b/tests/generic/062
> index 9024af2e..7e79a2dd 100755
> --- a/tests/generic/062
> +++ b/tests/generic/062
> @@ -120,7 +120,7 @@ for nsp in $ATTR_MODES; do
> getfattr -m $nsp -e hex -n $nsp.name2 $SCRATCH_MNT/$inode 2>&1 | invalid_attribute_filter
>
> echo "*** final list (strings, type=$inode, nsp=$nsp)"
> - getfattr -m '.' -e hex $SCRATCH_MNT/$inode
> + getfattr -m '.' -e hex $SCRATCH_MNT/$inode | grep -ve "security\.selinux"
>
> done
> done
> diff --git a/tests/generic/377 b/tests/generic/377
> index f7835ee8..0ce2cb4b 100755
> --- a/tests/generic/377
> +++ b/tests/generic/377
> @@ -66,7 +66,7 @@ $listxattr $testfile 9
> $listxattr $testfile 11
>
> # 6. Calling listxattr with buffersize bigger than needed should succeed.
> -$listxattr $testfile 500 | sort
> +$listxattr $testfile 500 | grep -ve "security\.selinux" | sort
>
> status=0
> exit
> --
> 2.18.1
>
prev parent reply other threads:[~2018-11-28 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 21:43 [PATCH 0/3] Adapt some tests to ChromeOS Gwendal Grignou
2018-11-27 21:43 ` [PATCH 1/3] generic: workaround device where glibc is not installed Gwendal Grignou
2018-11-28 3:30 ` Eryu Guan
2018-11-29 2:10 ` Dave Chinner
2018-11-30 6:37 ` Eryu Guan
2018-11-27 21:43 ` [PATCH 2/3] ext4: 032: fail nicely if the test partition is not big enough for the test Gwendal Grignou
2018-11-28 3:36 ` Eryu Guan
2018-11-27 21:43 ` [PATCH 3/3] generic: exclude selinux xattr form being considered Gwendal Grignou
2018-11-28 4:37 ` Eryu Guan [this message]
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=20181128043705.GS3889@desktop \
--to=guaneryu@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=gwendal@chromium.org \
/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.