From: "Cui, Yue/崔 悦" <cuiyue-fnst@fujitsu.com>
To: <fstests@vger.kernel.org>, <linux-nfs@vger.kernel.org>
Subject: [PATCH] generic: Ignore getcap and setcap cases when it is NFS
Date: Mon, 5 Sep 2022 14:22:45 +0800 [thread overview]
Message-ID: <2a35a5a9-945a-e8ac-67e3-2fb312e41a46@fujitsu.com> (raw)
In-Reply-To: <>
Signed-off-by: Cui Yue <cuiyue-fnst@fujitsu.com>
---
tests/generic/513 | 2 ++
tests/generic/675 | 2 ++
tests/generic/688 | 2 ++
3 files changed, 6 insertions(+)
diff --git a/tests/generic/513 b/tests/generic/513
index dc08278..d7201f5 100755
--- a/tests/generic/513
+++ b/tests/generic/513
@@ -19,6 +19,8 @@ _require_scratch_reflink
_require_command "$GETCAP_PROG" getcap
_require_command "$SETCAP_PROG" setcap
+test $FSTYP == "nfs" && _notrun "NFS can't support getcap and setcap"
+
_scratch_mkfs >>$seqres.full 2>&1
_scratch_mount
diff --git a/tests/generic/675 b/tests/generic/675
index 189251f..0e9fd36 100755
--- a/tests/generic/675
+++ b/tests/generic/675
@@ -22,6 +22,8 @@ _require_command "$GETCAP_PROG" getcap
_require_command "$SETCAP_PROG" setcap
_require_scratch_reflink
+test $FSTYP == "nfs" && _notrun "NFS can't support getcap and setcap"
+
_scratch_mkfs >> $seqres.full
_scratch_mount
_require_congruent_file_oplen $SCRATCH_MNT 1048576
diff --git a/tests/generic/688 b/tests/generic/688
index 426286b..54b9e3c 100755
--- a/tests/generic/688
+++ b/tests/generic/688
@@ -30,6 +30,8 @@ _require_xfs_io_command falloc
_require_test
_require_congruent_file_oplen $TEST_DIR 65536
+test $FSTYP == "nfs" && _notrun "NFS can't support getcap and setcap"
+
junk_dir=$TEST_DIR/$seq
junk_file=$junk_dir/a
mkdir -p $junk_dir/
--
1.8.3.1
reply other threads:[~2022-09-05 6:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2a35a5a9-945a-e8ac-67e3-2fb312e41a46@fujitsu.com \
--to=cuiyue-fnst@fujitsu.com \
--cc=fstests@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox