From: Qu Wenruo <wqu@suse.com>
To: Naohiro Aota <naohiro.aota@wdc.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 3/4] btrfs-progs: tests: add wait_for_nullbdevs
Date: Wed, 10 Sep 2025 14:52:51 +0930 [thread overview]
Message-ID: <5ca0a200-8a17-49ce-8864-e28959ed308e@suse.com> (raw)
In-Reply-To: <20250910050412.2138579-4-naohiro.aota@wdc.com>
在 2025/9/10 14:34, Naohiro Aota 写道:
> It is a nullb version of wait_for_loopdevs. It waits for all the nullb
> devices are ready to use.
>
> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> tests/common | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/tests/common b/tests/common
> index 2c90acb90cfc..42733c215f96 100644
> --- a/tests/common
> +++ b/tests/common
> @@ -984,6 +984,14 @@ cleanup_nullbdevs()
> name=$(basename "$dev")
> run_check $SUDO_HELPER "$nullb" rm "$name"
> done
> + unset nullb_devs
> +}
> +
> +wait_for_nullbdevs()
> +{
> + for dev in ${nullb_devs[@]}; do
> + run_mayfail $SUDO_HELPER "$TOP/btrfs" device ready "$dev"
> + done
> }
>
> init_env()
next prev parent reply other threads:[~2025-09-10 5:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 5:04 [PATCH v2 0/4] btrfs-progs: tests: add new mkfs test for zoned device Naohiro Aota
2025-09-10 5:04 ` [PATCH v2 1/4] btrfs-progs: tests: output error/warn message to stderr Naohiro Aota
2025-09-10 5:22 ` Qu Wenruo
2025-09-10 5:04 ` [PATCH v2 2/4] btrfs-progs: tests: check nullb index for the error case Naohiro Aota
2025-09-10 5:22 ` Qu Wenruo
2025-09-10 5:04 ` [PATCH v2 3/4] btrfs-progs: tests: add wait_for_nullbdevs Naohiro Aota
2025-09-10 5:22 ` Qu Wenruo [this message]
2025-09-10 5:04 ` [PATCH v2 4/4] btrfs-progs: tests: add new mkfs test for zoned device Naohiro Aota
2025-10-16 17:53 ` [PATCH v2 0/4] " David Sterba
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=5ca0a200-8a17-49ce-8864-e28959ed308e@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
/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