From: Mikulas Patocka <mpatocka@redhat.com>
To: Yu Kuai <yukuai3@huawei.com>, Song Liu <song@kernel.org>,
David Jeffery <djeffery@redhat.com>,
Li Nan <linan122@huawei.com>
Cc: dm-devel@lists.linux.dev, linux-raid@vger.kernel.org,
Mike Snitzer <msnitzer@redhat.com>,
Heinz Mauelshagen <heinzm@redhat.com>,
Benjamin Marzinski <bmarzins@redhat.com>
Subject: [PATCH 3/7] md: test for MD_RECOVERY_DONE in stop_sync_thread
Date: Wed, 17 Jan 2024 19:19:26 +0100 (CET) [thread overview]
Message-ID: <9801e40-8ac7-e225-6a71-309dcf9dc9aa@redhat.com> (raw)
In-Reply-To: <e5e8afe2-e9a8-49a2-5ab0-958d4065c55e@redhat.com>
stop_sync_thread sets MD_RECOVERY_INTR and then waits for
MD_RECOVERY_RUNNING to be cleared. However, md_do_sync will not clear
MD_RECOVERY_RUNNING when exiting, it will set MD_RECOVERY_DONE instead.
So, we must wait for MD_RECOVERY_DONE to be set as well.
This patch fixes a deadlock in the LVM2 test shell/integrity-caching.sh.
sysrq: Show Blocked State
task:lvm state:D stack:0 pid:11422 tgid:11422 ppid:1374 flags:0x00004002
Call Trace:
<TASK>
__schedule+0x228/0x570
schedule+0x29/0xa0
schedule_timeout+0x6a/0xd0
? timer_shutdown_sync+0x10/0x10
stop_sync_thread+0x141/0x180 [md_mod]
? housekeeping_test_cpu+0x30/0x30
__md_stop_writes+0x10/0xd0 [md_mod]
md_stop+0x9/0x20 [md_mod]
raid_dtr+0x1e/0x60 [dm_raid]
dm_table_destroy+0x53/0x110 [dm_mod]
__dm_destroy+0x10b/0x1e0 [dm_mod]
? table_clear+0xa0/0xa0 [dm_mod]
dev_remove+0xd4/0x110 [dm_mod]
ctl_ioctl+0x2e1/0x570 [dm_mod]
dm_ctl_ioctl+0x5/0x10 [dm_mod]
__x64_sys_ioctl+0x85/0xa0
do_syscall_64+0x5d/0x1a0
entry_SYSCALL_64_after_hwframe+0x46/0x4e
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org # v6.7
Fixes: 130443d60b1b ("md: refactor idle/frozen_sync_thread() to fix deadlock")
---
drivers/md/md.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index: linux-2.6/drivers/md/md.c
===================================================================
--- linux-2.6.orig/drivers/md/md.c
+++ linux-2.6/drivers/md/md.c
@@ -4881,7 +4881,8 @@ static void stop_sync_thread(struct mdde
if (check_seq)
sync_seq = atomic_read(&mddev->sync_seq);
- if (!test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)) {
+ if (!test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) ||
+ test_bit(MD_RECOVERY_DONE, &mddev->recovery)) {
if (!locked)
mddev_unlock(mddev);
return;
@@ -4901,6 +4902,7 @@ retry:
if (!wait_event_timeout(resync_wait,
!test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) ||
+ test_bit(MD_RECOVERY_DONE, &mddev->recovery) ||
(check_seq && sync_seq != atomic_read(&mddev->sync_seq)),
HZ / 10))
goto retry;
next prev parent reply other threads:[~2024-01-17 18:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 18:16 [PATCH 0/7] MD fixes for the LVM2 testsuite Mikulas Patocka
2024-01-17 18:17 ` [PATCH 1/7] md: Revert fa2bbff7b0b4 ("md: synchronize flush io with array reconfiguration") Mikulas Patocka
2024-01-18 1:27 ` Yu Kuai
2024-01-17 18:18 ` [PATCH 2/7] md: fix a race condition when stopping the sync thread Mikulas Patocka
2024-01-18 1:32 ` Yu Kuai
2024-01-18 13:07 ` Mikulas Patocka
2024-01-18 13:20 ` Yu Kuai
2024-01-18 13:28 ` Mikulas Patocka
2024-01-17 18:19 ` Mikulas Patocka [this message]
2024-01-18 0:19 ` [PATCH 3/7] md: test for MD_RECOVERY_DONE in stop_sync_thread Song Liu
2024-01-18 13:23 ` Mikulas Patocka
2024-01-18 21:10 ` Song Liu
2024-01-22 16:34 ` Mikulas Patocka
2024-01-23 2:31 ` Benjamin Marzinski
2024-01-26 9:17 ` Yu Kuai
2024-01-26 9:37 ` Yu Kuai
2024-01-26 10:29 ` Zdenek Kabelac
2024-01-27 1:13 ` Yu Kuai
2024-01-27 1:19 ` Yu Kuai
2024-01-18 1:35 ` Yu Kuai
2024-01-17 18:20 ` [PATCH 4/7] md: call md_reap_sync_thread from __md_stop_writes Mikulas Patocka
2024-01-18 1:38 ` Yu Kuai
2024-01-17 18:21 ` [PATCH 5/7] md: fix deadlock in shell/lvconvert-raid-reshape-linear_to_raid6-single-type.sh Mikulas Patocka
2024-01-18 1:12 ` Song Liu
2024-01-18 1:51 ` Yu Kuai
2024-01-17 18:22 ` [PATCH 6/7] md: partially revert "md/raid6: use valid sector values to determine if an I/O should wait on the reshape" Mikulas Patocka
2024-01-17 23:56 ` Song Liu
2024-01-17 18:22 ` [PATCH 7/7] md: fix a suspicious RCU usage warning Mikulas Patocka
2024-01-17 23:59 ` Song Liu
2024-01-18 1:56 ` Yu Kuai
2024-01-25 17:31 ` Song Liu
2024-01-17 19:27 ` [PATCH 0/7] MD fixes for the LVM2 testsuite Song Liu
2024-01-18 2:03 ` Yu Kuai
2024-01-27 7:57 ` Yu Kuai
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=9801e40-8ac7-e225-6a71-309dcf9dc9aa@redhat.com \
--to=mpatocka@redhat.com \
--cc=bmarzins@redhat.com \
--cc=djeffery@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=heinzm@redhat.com \
--cc=linan122@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=msnitzer@redhat.com \
--cc=song@kernel.org \
--cc=yukuai3@huawei.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