From: Christoph Hellwig <hch@infradead.org>
To: Anand Jain <asj@kernel.org>
Cc: zlang@kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: fix flaky device name in _cleanup_flakey
Date: Wed, 17 Dec 2025 21:29:31 -0800 [thread overview]
Message-ID: <aUORO1y4rkXHAH-f@infradead.org> (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.
This looks good, but I vaguely remember fixing this up on the go, and
seeing random hangs. While that could have been me fat-fingering
something, please run all the tests using this first to make sure it
works just to be safe.
next prev parent reply other threads:[~2025-12-18 5:29 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
2025-12-18 5:29 ` Christoph Hellwig [this message]
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=aUORO1y4rkXHAH-f@infradead.org \
--to=hch@infradead.org \
--cc=asj@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