From: Zorro Lang <zlang@kernel.org>
To: Liu Yiding <liuyd.fnst@fujitsu.com>
Cc: fstests@vger.kernel.org, djwong@kernel.org
Subject: Re: [PATCH] generic/688: Skip test if fs doesn't support security
Date: Tue, 2 Aug 2022 17:17:00 +0800 [thread overview]
Message-ID: <20220802091700.d2e3u7defue7kwbd@zlang-mailbox> (raw)
In-Reply-To: <1659426760-2-1-git-send-email-liuyd.fnst@fujitsu.com>
On Tue, Aug 02, 2022 at 07:52:40AM +0000, Liu Yiding wrote:
> This test require security attr. Skip test if fs doesn't support
> security attr. E.g. virtiofs
>
> Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com>
> ---
Hmm... looks like we can re-start this discussion long time ago:
https://lore.kernel.org/fstests/20220323023845.saj5en74km7aibdx@zlang-mailbox/
About how can we deal with those fs doesn't support capabilities, e.g. nfs, virtiofs??
Thanks,
Zorro
> tests/generic/688 | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/generic/688 b/tests/generic/688
> index 426286b6..d11b4c21 100755
> --- a/tests/generic/688
> +++ b/tests/generic/688
> @@ -7,6 +7,7 @@
> # Functional test for dropping capability bits as part of an fallocate.
> #
> . ./common/preamble
> +. ./common/attr
> _begin_fstest auto prealloc quick
>
> # Override the default cleanup function.
> @@ -28,6 +29,7 @@ _require_command "$GETCAP_PROG" getcap
> _require_command "$SETCAP_PROG" setcap
> _require_xfs_io_command falloc
> _require_test
> +_require_attrs security
> _require_congruent_file_oplen $TEST_DIR 65536
>
> junk_dir=$TEST_DIR/$seq
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-08-02 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 7:52 [PATCH] generic/688: Skip test if fs doesn't support security Liu Yiding
2022-08-02 9:17 ` Zorro Lang [this message]
2022-08-03 6:48 ` liuyd.fnst
2022-08-03 10:40 ` Zorro Lang
2022-08-04 1:32 ` liuyd.fnst
2022-08-02 22:05 ` Dave Chinner
2022-08-03 6:45 ` liuyd.fnst
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=20220802091700.d2e3u7defue7kwbd@zlang-mailbox \
--to=zlang@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=liuyd.fnst@fujitsu.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