FS/XFS testing framework
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-nfs@vger.kernel.org, Zorro Lang <zlang@redhat.com>,
	Jeff Layton <jlayton@kernel.org>
Subject: [PATCH fstests v2 2/3] generic/357: don't run this test on NFS
Date: Fri, 01 Sep 2023 13:39:56 -0400	[thread overview]
Message-ID: <20230901-nfs-skip-v2-2-9eccd59bc524@kernel.org> (raw)
In-Reply-To: <20230901-nfs-skip-v2-0-9eccd59bc524@kernel.org>

NFS doesn't keep track of whether a file is reflinked or not, so it
doesn't prevent this behavior. It shouldn't be a problem for NFS anyway,
so just skip this test there.

Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
 tests/generic/357 | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tests/generic/357 b/tests/generic/357
index ce748f854327..a0299b32bc90 100755
--- a/tests/generic/357
+++ b/tests/generic/357
@@ -24,6 +24,11 @@ _cleanup()
 . ./common/reflink
 
 # real QA test starts here
+
+# For NFS, a reflink is just a CLONE operation, and after that
+# point it's dealt with by the server.
+_supported_fs ^nfs generic
+
 _require_scratch_swapfile
 _require_scratch_reflink
 _require_cp_reflink

-- 
2.41.0


  parent reply	other threads:[~2023-09-01 17:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 17:39 [PATCH fstests v2 0/3] generic: skip a few tests on NFS Jeff Layton
2023-09-01 17:39 ` [PATCH fstests v2 1/3] generic/294: don't run this test " Jeff Layton
2023-09-01 19:19   ` Zorro Lang
2023-09-01 19:37     ` Jeff Layton
2023-09-01 17:39 ` Jeff Layton [this message]
2023-09-01 17:39 ` [PATCH fstests v2 3/3] generic/187: " Jeff Layton

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=20230901-nfs-skip-v2-2-9eccd59bc524@kernel.org \
    --to=jlayton@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-nfs@vger.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