From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: fstests@vger.kernel.org, zlang@kernel.org
Subject: Re: [PATCH v3 3/4] generic/452: make coping work with multi-call binary
Date: Fri, 25 Sep 2026 13:02:45 -0700 [thread overview]
Message-ID: <20260925200245.GL6253@frogsfrogsfrogs> (raw)
In-Reply-To: <20260925104514.664260-4-aalbersh@kernel.org>
On Fri, Sep 25, 2026 at 12:45:11PM +0200, Andrey Albershteyn wrote:
> On some system coreutils binaries are all symlink to the single
> coreutils binary. Just copying 'ls' will not work in this setup,
> especially, with the different binary name.
>
> Add 'realpath' to find out the real binary is make it behave like an
> 'ls' by renaming it to 'ls'.
>
> Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
Seems fine to me, though I wonder if we should change this to copy
/bin/echo instead of ls so that the output is more stable...
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> tests/generic/452 | 7 +++++--
> tests/generic/452.out | 4 ++--
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/tests/generic/452 b/tests/generic/452
> index a19a79623489..604d978cd98c 100755
> --- a/tests/generic/452
> +++ b/tests/generic/452
> @@ -24,8 +24,11 @@ _exclude_scratch_mount_option "noexec"
> _scratch_mkfs > $seqres.full 2>&1
> _scratch_mount >> $seqres.full 2>&1
>
> -LS="$(type -P ls)"
> -SCRATCH_LS=$SCRATCH_MNT/ls_on_scratch
> +# Resolve full absolute path to the ls binary. This is necessary for multi-call
> +# binaries. In multi-call binary setup "ls" is just a symlink to a binary (e.g.
> +# coreutils) which behaves as "ls" based on the executable name (first arg $0).
> +LS="$(realpath $(type -P ls))"
> +SCRATCH_LS=$SCRATCH_MNT/ls
> cp $LS $SCRATCH_LS
>
> $SCRATCH_LS $SCRATCH_LS | _filter_scratch
> diff --git a/tests/generic/452.out b/tests/generic/452.out
> index 1d24d6b3c83a..436a01e13b09 100644
> --- a/tests/generic/452.out
> +++ b/tests/generic/452.out
> @@ -1,3 +1,3 @@
> QA output created by 452
> -SCRATCH_MNT/ls_on_scratch
> -SCRATCH_MNT/ls_on_scratch
> +SCRATCH_MNT/ls
> +SCRATCH_MNT/ls
> --
> 2.54.0
>
>
next prev parent reply other threads:[~2026-09-25 20:02 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 [this message]
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 ` [PATCH v3 0/4] xfstests: random fixes Zorro Lang
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=20260925200245.GL6253@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=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