From: Andrey Albershteyn <aalbersh@kernel.org>
To: fstests@vger.kernel.org, zlang@kernel.org
Cc: Andrey Albershteyn <aalbersh@kernel.org>
Subject: [PATCH v2 0/4] xfstests: random fixes
Date: Wed, 23 Sep 2026 11:32:51 +0200 [thread overview]
Message-ID: <20260923093259.16199-1-aalbersh@kernel.org> (raw)
Hi folks,
This series contain a few random fixes I apply for xfstests in my
immutable test machines. These make it easier to work with read-only
xfstests package.
Changes from v1:
- Add RvB
- Add comment in generic/452
Andrey Albershteyn (4):
xfs/071: use _link_out_link instead of opencoding file picking
common: link .out file to the output directory
generic/452: make coping work with multi-call binary
xfstests: fix permissions on system file installed by libtoolize
Makefile | 3 +++
check | 12 ++++++++----
common/rc | 4 ++--
tests/generic/452 | 7 +++++--
tests/generic/452.out | 4 ++--
tests/xfs/071 | 7 +++----
tests/xfs/071.cfg | 1 +
tests/xfs/{071.out.64 => 071.out.default} | 0
8 files changed, 24 insertions(+), 14 deletions(-)
create mode 100644 tests/xfs/071.cfg
rename tests/xfs/{071.out.64 => 071.out.default} (100%)
--
2.54.0
next 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 Andrey Albershteyn [this message]
2026-09-23 9:32 ` [PATCH v2 1/4] xfs/071: use _link_out_link instead of opencoding file picking Andrey Albershteyn
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-1-aalbersh@kernel.org \
--to=aalbersh@kernel.org \
--cc=fstests@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox