From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: fstests@vger.kernel.org, zlang@kernel.org
Subject: Re: [PATCH] _test_mkfs: Include external log device (if any) when creating fs on TEST_DEV
Date: Fri, 24 May 2024 08:07:02 -0700 [thread overview]
Message-ID: <20240524150702.GA52977@frogsfrogsfrogs> (raw)
In-Reply-To: <20240524073104.615253-1-chandanbabu@kernel.org>
On Fri, May 24, 2024 at 01:01:01PM +0530, Chandan Babu R wrote:
> Test execution fails when testing XFS with external log device and when
> RECREATE_TEST_DEV is set to true. This is because _test_mkfs() is invoked as
> part of recreating the filesystem on test device and this function does not
> include the external log device as part of the mkfs.xfs command line.
>
> _test_mount() invoked later fails since it passes an external log device to
> the mount syscall which the kernel does not expect to find.
>
> To fix this bug, this commit modifies _test_mkfs() to invoke _test_options()
> in order to compute the value of TEST_OPTIONS and includes the resulting value
> in the mkfs.xfs command line.
>
> Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
Doh
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> common/rc | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/common/rc b/common/rc
> index 0fe56382..6562ccd7 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -614,7 +614,8 @@ _test_mkfs()
> $MKFS_PROG -t $FSTYP -- -F $MKFS_OPTIONS $* $TEST_DEV
> ;;
> xfs)
> - $MKFS_PROG -t $FSTYP -- -f $MKFS_OPTIONS $* $TEST_DEV
> + _test_options mkfs
> + $MKFS_PROG -t $FSTYP -- -f $TEST_OPTIONS $MKFS_OPTIONS $* $TEST_DEV
> ;;
> bcachefs)
> $MKFS_BCACHEFS_PROG $MKFS_OPTIONS $* $TEST_DEV > /dev/null
> --
> 2.43.0
>
>
prev parent reply other threads:[~2024-05-24 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 7:31 [PATCH] _test_mkfs: Include external log device (if any) when creating fs on TEST_DEV Chandan Babu R
2024-05-24 8:06 ` Christoph Hellwig
2024-05-24 15:07 ` Darrick J. Wong [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=20240524150702.GA52977@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandanbabu@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 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.