From: Dave Chinner <david@fromorbit.com>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
dchinner@redhat.com, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] fstests: fix argument passing to _run_fsstress and _run_fsstress_bg
Date: Thu, 12 Dec 2024 13:31:02 +1100 [thread overview]
Message-ID: <Z1pK5j6A5aJJdilC@dread.disaster.area> (raw)
In-Reply-To: <51ccb57553e069946bec983ded52a75640d4fef5.1733851879.git.fdmanana@suse.com>
On Tue, Dec 10, 2024 at 05:32:54PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> After commit 8973af00ec21 ("fstests: cleanup fsstress process management")
> test cases btrfs/007 and btrfs/284 started to fail. For example:
>
> $ ./check btrfs/007
> FSTYP -- btrfs
> PLATFORM -- Linux/x86_64 debian0 6.13.0-rc1-btrfs-next-181+ #1 SMP PREEMPT_DYNAMIC Tue Dec 3 13:03:23 WET 2024
> MKFS_OPTIONS -- /dev/sdc
> MOUNT_OPTIONS -- /dev/sdc /home/fdmanana/btrfs-tests/scratch_1
>
> btrfs/007 1s ... [failed, exit status 1]- output mismatch (see /home/fdmanana/git/hub/xfstests/results//btrfs/007.out.bad)
> --- tests/btrfs/007.out 2020-06-10 19:29:03.810518987 +0100
> +++ /home/fdmanana/git/hub/xfstests/results//btrfs/007.out.bad 2024-12-10 16:09:56.345937619 +0000
> @@ -1,3 +1,4 @@
> QA output created by 007
> *** test send / receive
> -*** done
> +failed: '2097152000 200'
> +(see /home/fdmanana/git/hub/xfstests/results//btrfs/007.full for details)
> ...
> (Run 'diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/007.out /home/fdmanana/git/hub/xfstests/results//btrfs/007.out.bad' to see the entire diff)
> Ran: btrfs/007
>
> The problem comes from _run_fsstress and _run_fsstress_bg using $*, which
> splits the string argument for the -x command used by btrfs/007, so that
> fsstress gets the argument for -x as simply:
>
> "btrfs"
>
> Instead of:
>
> "btrfs subvolume snapshot -r $SCRATCH_MNT $SCRATCH_MNT/base"
>
> Fix this by using "$@" instead of $*.
>
> Fixes: 8973af00ec21 ("fstests: cleanup fsstress process management")
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
> common/rc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/common/rc b/common/rc
> index 1b2e4508..f4fff59b 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -78,13 +78,13 @@ _kill_fsstress()
> _run_fsstress_bg()
> {
> cp -f $FSSTRESS_PROG $_FSSTRESS_PROG
> - $_FSSTRESS_PROG $FSSTRESS_AVOID $* >> $seqres.full 2>&1 &
> + $_FSSTRESS_PROG $FSSTRESS_AVOID "$@" >> $seqres.full 2>&1 &
> _FSSTRESS_PID=$!
> }
>
> _run_fsstress()
> {
> - _run_fsstress_bg $*
> + _run_fsstress_bg "$@"
> _wait_for_fsstress
> return $?
> }
Looks good.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2024-12-12 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 17:32 [PATCH] fstests: fix argument passing to _run_fsstress and _run_fsstress_bg fdmanana
2024-12-12 2:31 ` Dave Chinner [this message]
2024-12-17 7:53 ` Qu Wenruo
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=Z1pK5j6A5aJJdilC@dread.disaster.area \
--to=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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