FS/XFS testing framework
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v3 0/4] xfstests: random fixes
Date: Sun, 27 Sep 2026 19:50:18 +0800	[thread overview]
Message-ID: <arkCzpcJlBYCU3yh@zlang-mailbox> (raw)
In-Reply-To: <20260925104514.664260-1-aalbersh@kernel.org>

On Fri, Sep 25, 2026 at 12:45:08PM +0200, Andrey Albershteyn wrote:
> 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 v2:
> - Remove .out.good before running the test
> - Fix "diff ..." message for tests with .out.good
> Changes from v1:
> - Add RvB
> - Add comment in generic/452

Thanks, this patchset is good to me now. I'll merge it.

Reviewed-by: Zorro Lang <zlang@kernel.org>

> 
> 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                                     | 14 +++++++++-----
>  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, 25 insertions(+), 15 deletions(-)
>  create mode 100644 tests/xfs/071.cfg
>  rename tests/xfs/{071.out.64 => 071.out.default} (100%)
> 
> -- 
> 2.54.0
> 

      parent reply	other threads:[~2026-09-27 11:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 10:45 [PATCH v3 0/4] xfstests: random fixes Andrey Albershteyn
2026-09-25 10:45 ` [PATCH v3 1/4] xfs/071: use _link_out_link instead of opencoding file picking Andrey Albershteyn
2026-09-25 20:03   ` Darrick J. Wong
2026-09-25 10:45 ` [PATCH v3 2/4] common: link .out file to the output directory Andrey Albershteyn
2026-09-25 20:04   ` Darrick J. Wong
2026-09-25 10:45 ` [PATCH v3 3/4] generic/452: make coping work with multi-call binary Andrey Albershteyn
2026-09-25 20:02   ` Darrick J. Wong
2026-09-25 10:45 ` [PATCH v3 4/4] xfstests: fix permissions on system file installed by libtoolize Andrey Albershteyn
2026-09-25 20:04   ` Darrick J. Wong
2026-09-27 11:50 ` Zorro Lang [this message]

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=arkCzpcJlBYCU3yh@zlang-mailbox \
    --to=zlang@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=fstests@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