From: "Darrick J. Wong" <djwong@kernel.org>
To: Anand Jain <asj@kernel.org>
Cc: zlang@kernel.org, hch@lst.de, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: fix flaky device name in _cleanup_flakey
Date: Wed, 17 Dec 2025 09:45:31 -0800 [thread overview]
Message-ID: <20251217174531.GK7716@frogsfrogsfrogs> (raw)
In-Reply-To: <6025643af0c6a7d7d377aef22a53f23f24f06db6.1765988375.git.asj@kernel.org>
On Thu, Dec 18, 2025 at 01:00:22AM +0800, Anand Jain wrote:
> There is no device named flakey-test, which _cleanup_flakey() currently
> uses. The actual device name is stored in $FLAKEY_NAME and is set to
> flakey-test.$seq. Use $FLAKEY_NAME instead.
>
> Signed-off-by: Anand Jain <asj@kernel.org>
Ugh, still finding obvious bugs a year later <grumble>
Cc: <fstests@vger.kernel.org> # v2024.12.08
Fixes: 603030dee015ba ("fstests: per-test dmflakey instances")
Thanks for spotting this, Anand.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> (apply this on top of the patchset
> 'stop overriding SCRATCH_{,LOG,RT}DEV v2')
> common/dmflakey | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/common/dmflakey b/common/dmflakey
> index cb0359901c16..6ac666f5b61e 100644
> --- a/common/dmflakey
> +++ b/common/dmflakey
> @@ -76,7 +76,7 @@ _cleanup_flakey()
> # otherwise the umount will hang
> test -n "$NON_FLAKEY_LOGDEV" && $DMSETUP_PROG resume $FLAKEY_LOGNAME &> /dev/null
> test -n "$NON_FLAKEY_RTDEV" && $DMSETUP_PROG resume $FLAKEY_RTNAME &> /dev/null
> - test -n "$NON_FLAKEY_DEV" && $DMSETUP_PROG resume flakey-test > /dev/null 2>&1
> + test -n "$NON_FLAKEY_DEV" && $DMSETUP_PROG resume $FLAKEY_NAME &> /dev/null
>
> _unmount $SCRATCH_MNT > /dev/null 2>&1
>
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2025-12-17 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 17:00 [PATCH] fstests: fix flaky device name in _cleanup_flakey Anand Jain
2025-12-17 17:45 ` Darrick J. Wong [this message]
2025-12-18 5:29 ` Christoph Hellwig
2025-12-18 6:11 ` Anand Jain
2025-12-18 6:13 ` Christoph Hellwig
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=20251217174531.GK7716@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=asj@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--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