From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests <fstests@vger.kernel.org>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] generic/805: skip this test if we can't mount the filesystem
Date: Wed, 14 Oct 2026 20:31:06 -0700 [thread overview]
Message-ID: <20261015033106.GU6253@frogsfrogsfrogs> (raw)
In-Reply-To: <20260924060245.GE6253@frogsfrogsfrogs>
On Wed, Sep 23, 2026 at 11:02:45PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> This test doesn't work on filesystems with external devices (e.g. xfs
> realtime) because the SCRATCH_DEV gets formatted with regular scratch fs
> options but the filesystem is mounted with a bare _mount call, not
> _scratch_mount. Since SCRATCH_DEV is not the dm-linear device created
> earlier in the test, we can't really use that either.
>
> In any case, if we can't mount the filesystem immediately after
> formatting it, then we're not satisfying a test precondition. Change
> the _fail to _notrun.
>
> While we're at it, fix the cleanup function so that unmount failures
> don't pollute the output.
>
> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
> tests/generic/805 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/generic/805 b/tests/generic/805
> index ae498f5c669808..403d36d383a973 100755
> --- a/tests/generic/805
> +++ b/tests/generic/805
> @@ -25,7 +25,7 @@ _cleanup()
> {
> xfs_freeze -u $SCRATCH_MNT 2>/dev/null
> $DMSETUP_PROG resume $lvdev >> $seqres.full 2>&1
> - _unmount -q $SCRATCH_MNT
> + _unmount -q $SCRATCH_MNT &>> $seqres.full
Still seeing the false failures as a result of the lack of redirection
here, so I'll send just this chunk as a separate patch.
--D
> _dmsetup_remove $node
> cd /
> rm -f $tmp.*
> @@ -47,7 +47,7 @@ table="0 $size_in_sector linear $SCRATCH_DEV 0"
> _dmsetup_create $node --table "$table" || \
> _fail "failed to create dm device"
>
> -_mount $lvdev $SCRATCH_MNT || _fail "failed to mount dm device"
> +_mount $lvdev $SCRATCH_MNT || _notrun "failed to mount dm device"
>
> # Freeze the filesystem from userspace first, then nest a block device
> # initiated freeze/thaw cycle inside it via dm suspend/resume.
>
prev parent reply other threads:[~2026-10-15 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 6:02 [PATCH] generic/805: skip this test if we can't mount the filesystem Darrick J. Wong
2026-09-24 11:38 ` Andrey Albershteyn
2026-09-25 4:58 ` Christoph Hellwig
2026-09-25 14:49 ` Darrick J. Wong
2026-10-15 3:31 ` 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=20261015033106.GU6253@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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.