From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Jack Wang <jinpu.wang@ionos.com>
Cc: linux-block@vger.kernel.org, Jack Wang <jinpu.wang@cloud.ionos.com>
Subject: Re: [PATCH blktests] tests/md: add test 005 for raid1 deadlock under I/O, limit changes and recovery
Date: Wed, 23 Sep 2026 14:28:24 +0900 [thread overview]
Message-ID: <arNiSSZ37GJF431J@shinmob> (raw)
In-Reply-To: <20260910100916.1638378-1-jinpu.wang@ionos.com>
On Sep 10, 2026 / 12:09, Jack Wang wrote:
> From: Jack Wang <jinpu.wang@cloud.ionos.com>
>
> Add a regression test for a deadlock reported against raid1 with an
> internal bitmap, where concurrent I/O, queue limit updates
> (max_sectors_kb) and device fail/remove/add (recovery) cycles can
> deadlock.
>
> The test creates a raid1 array with an internal bitmap on two brd
> devices, drives it with fio while repeatedly toggling
> max_sectors_kb and cycling one member through fail/remove/add, and
> flags a likely deadlock if any of these steps fail to make progress
> within a bounded timeout.
>
> Link: https://lore.kernel.org/linux-raid/CAMGffE=heGA3y8FjQ0Sm1jj-kd-=H9Y54WozKASSEZhc9UNKjA@mail.gmail.com/T/#t
> Signed-off-by: Jack Wang <jinpu.wang@cloud.ionos.com>
Thanks for the patch. Overall, the patch looks good to me. I have one comment in
line. Also, I ran the test case on v7.3-rc4 kernel, and confirmed it avois the
hang. When I applied the kernel side fix v2 series [*] on top of v7.3-rc4
kernel, and confirmed that the test case passes. Good.
[*] https://lore.kernel.org/linux-block/20260910081114.1605746-1-jinpu.wang@ionos.com/
I will wait for the kernel side patches get settled on Linus master branch
before applying this patch. Thanks!
[...]
> diff --git a/tests/md/005 b/tests/md/005
> new file mode 100755
> index 000000000000..5493d0edc933
> --- /dev/null
> +++ b/tests/md/005
> @@ -0,0 +1,142 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-3.0+
> +# Copyright (C) 2026 Jack Wang
> +#
> +# Regression test for a deadlock reported against raid1 with an internal
> +# bitmap, where concurrent I/O, queue limit updates (max_sectors_kb) and
> +# device fail/remove/add cycles (recovery) can deadlock.
> +#
> +# See: https://lore.kernel.org/linux-raid/CAMGffE=heGA3y8FjQ0Sm1jj-kd-=H9Y54WozKASSEZhc9UNKjA@mail.gmail.com/T/#t
> +
> +. tests/md/rc
> +. common/brd
> +. common/fio
> +
> +DESCRIPTION="test for raid1 deadlock with internal bitmap under I/O, queue limit changes and fail/remove/add"
This description line looks a bit lengthy. How about to make it shorter as
follows?
"raid1 internal bitmap race among I/O, queue limit changes and fail/remove/add"
If you are okay with it, I can fold in the change when I apply the patch.
next prev parent reply other threads:[~2026-09-23 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 10:09 [PATCH blktests] tests/md: add test 005 for raid1 deadlock under I/O, limit changes and recovery Jack Wang
2026-09-23 5:28 ` Shin'ichiro Kawasaki [this message]
2026-09-23 13:08 ` Jinpu Wang
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=arNiSSZ37GJF431J@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=jinpu.wang@ionos.com \
--cc=linux-block@vger.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