From: "liuyd.fnst@fujitsu.com" <liuyd.fnst@fujitsu.com>
To: Zorro Lang <zlang@redhat.com>
Cc: Zorro Lang <zlang@kernel.org>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"djwong@kernel.org" <djwong@kernel.org>
Subject: Re: [PATCH] generic/688: Skip test if fs doesn't support security
Date: Thu, 4 Aug 2022 01:32:32 +0000 [thread overview]
Message-ID: <f6d185e8-beee-a0d7-f07f-1e1ffef99635@fujitsu.com> (raw)
In-Reply-To: <20220803104027.c5nme65zgwzccut5@zlang-mailbox>
On 8/3/22 18:40, Zorro Lang wrote:
> On Wed, Aug 03, 2022 at 06:48:47AM +0000, liuyd.fnst@fujitsu.com wrote:
>> Hi Zorro
>>
>> On 8/2/22 17:17, Zorro Lang wrote:
>>> 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??
>>
>> Ahh, so I don't need to send a v2 patch until you finish above discussion.
>
> Actually I'm not sure if we need a _require_capabilities(), or just use
> "_require_attrs security" for all filesystems which support/unsupport
> capabilities. Hope to hear more points.
>
I think a _require_capabilities() is much better than
"_require_attrs security()".
> If you'd like to send v2, there's not only g/688 need capabilities.
>
> Thanks,
> Zorro
>
>>
>>>
>>> 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-04 1:33 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
2022-08-03 6:48 ` liuyd.fnst
2022-08-03 10:40 ` Zorro Lang
2022-08-04 1:32 ` liuyd.fnst [this message]
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=f6d185e8-beee-a0d7-f07f-1e1ffef99635@fujitsu.com \
--to=liuyd.fnst@fujitsu.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=zlang@kernel.org \
--cc=zlang@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