From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, zlang@redhat.com
Cc: linux-xfs@vger.kernel.org, guan@eryu.me, fstests@vger.kernel.org
Subject: [PATCH 1/2] xfs/601: move this to tests/generic
Date: Mon, 20 Nov 2023 11:35:14 -0800 [thread overview]
Message-ID: <170050891446.536459.11166010762932928186.stgit@frogsfrogsfrogs> (raw)
In-Reply-To: <170050890870.536459.4420904342934916414.stgit@frogsfrogsfrogs>
From: Darrick J. Wong <djwong@kernel.org>
As per last week's discussion, xfs/601 doesn't have any xfs-specific
functionality in it. Turn it into a generic test.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
tests/generic/734 | 3 ++-
tests/generic/734.out | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
rename tests/{xfs/601 => generic/734} (98%)
rename tests/{xfs/601.out => generic/734.out} (78%)
diff --git a/tests/xfs/601 b/tests/generic/734
similarity index 98%
rename from tests/xfs/601
rename to tests/generic/734
index 9df46e5ebe..93c2ad90e3 100755
--- a/tests/xfs/601
+++ b/tests/generic/734
@@ -2,7 +2,7 @@
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2023 Oracle. All Rights Reserved.
#
-# FS QA Test No. 601
+# FS QA Test No. 734
#
# This is a regression test for the kernel commit noted below. The stale
# memory exposure can be exploited by creating a file with shared blocks,
@@ -29,6 +29,7 @@ _fixed_by_git_commit kernel 35d30c9cf127 \
"iomap: don't skip reading in !uptodate folios when unsharing a range"
# real QA test starts here
+_supported_fs generic
_require_test_reflink
_require_cp_reflink
_require_xfs_io_command "funshare"
diff --git a/tests/xfs/601.out b/tests/generic/734.out
similarity index 78%
rename from tests/xfs/601.out
rename to tests/generic/734.out
index 34d519ca46..174c3f82cb 100644
--- a/tests/xfs/601.out
+++ b/tests/generic/734.out
@@ -1,4 +1,4 @@
-QA output created by 601
+QA output created by 734
Create the original file and a clone
Funshare at least one pagecache page
Check contents
next prev parent reply other threads:[~2023-11-20 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 19:35 [PATCHSET 0/2] fstests: random fixes for v2023.11.19 Darrick J. Wong
2023-11-20 19:35 ` Darrick J. Wong [this message]
2023-11-21 4:35 ` [PATCH 1/2] xfs/601: move this to tests/generic Christoph Hellwig
2023-11-20 19:35 ` [PATCH 2/2] xfs/604: add missing falloc test Darrick J. Wong
2023-11-21 4:35 ` Christoph Hellwig
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=170050891446.536459.11166010762932928186.stgit@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-xfs@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