From: Andrey Albershteyn <aalbersh@kernel.org>
To: fstests@vger.kernel.org, zlang@kernel.org
Cc: Andrey Albershteyn <aalbersh@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: [PATCH v2 1/4] xfs/071: use _link_out_link instead of opencoding file picking
Date: Wed, 23 Sep 2026 11:32:52 +0200 [thread overview]
Message-ID: <20260923093259.16199-2-aalbersh@kernel.org> (raw)
In-Reply-To: <20260923093259.16199-1-aalbersh@kernel.org>
There's function which handles picking the right output file based on
the .cfg.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
---
tests/xfs/071 | 7 +++----
tests/xfs/071.cfg | 1 +
tests/xfs/{071.out.64 => 071.out.default} | 0
3 files changed, 4 insertions(+), 4 deletions(-)
create mode 100644 tests/xfs/071.cfg
rename tests/xfs/{071.out.64 => 071.out.default} (100%)
diff --git a/tests/xfs/071 b/tests/xfs/071
index c4722f67181a..47874e505c01 100755
--- a/tests/xfs/071
+++ b/tests/xfs/071
@@ -5,7 +5,6 @@
# FS QA Test No. 071
#
# Exercise IO at large file offsets.
-seqfull=$0
. ./common/preamble
_begin_fstest rw auto
@@ -22,11 +21,11 @@ _cleanup()
bitsperlong=`$here/src/feature -w`
# link correct .out file
-rm -f $seqfull.out
+seqfull=$0
if [ "$bitsperlong" -eq 32 ]; then
- ln -s $seq.out.32 $seqfull.out
+ _link_out_file "32"
else
- ln -s $seq.out.64 $seqfull.out
+ _link_out_file ""
fi
_filter_io()
diff --git a/tests/xfs/071.cfg b/tests/xfs/071.cfg
new file mode 100644
index 000000000000..e806b07bc08b
--- /dev/null
+++ b/tests/xfs/071.cfg
@@ -0,0 +1 @@
+32: 32
diff --git a/tests/xfs/071.out.64 b/tests/xfs/071.out.default
similarity index 100%
rename from tests/xfs/071.out.64
rename to tests/xfs/071.out.default
--
2.54.0
next prev parent reply other threads:[~2026-09-23 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 9:32 [PATCH v2 0/4] xfstests: random fixes Andrey Albershteyn
2026-09-23 9:32 ` Andrey Albershteyn [this message]
2026-09-23 9:32 ` [PATCH v2 2/4] common: link .out file to the output directory Andrey Albershteyn
2026-09-23 10:42 ` Zorro Lang
2026-09-23 12:28 ` Andrey Albershteyn
2026-09-23 15:18 ` Darrick J. Wong
2026-09-24 13:25 ` Zorro Lang
2026-09-23 9:32 ` [PATCH v2 3/4] generic/452: make coping work with multi-call binary Andrey Albershteyn
2026-09-23 9:32 ` [PATCH v2 4/4] xfstests: fix permissions on system file installed by libtoolize Andrey Albershteyn
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=20260923093259.16199-2-aalbersh@kernel.org \
--to=aalbersh@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=zlang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.