public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
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 2/7] md: fix a race condition when stopping the sync thread
Date: Wed, 17 Jan 2024 19:18:47 +0100 (CET)	[thread overview]
Message-ID: <8fb335e-6d2c-dbb5-d7-ded8db5145a@redhat.com> (raw)
In-Reply-To: <e5e8afe2-e9a8-49a2-5ab0-958d4065c55e@redhat.com>

Note that md_wakeup_thread_directly is racy - it will do nothing if the
thread is already running or it may cause spurious wake-up if the thread
is blocked in another subsystem.

In order to eliminate the race condition, we will retry
md_wakeup_thread_directly after 0.1 seconds.

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 |    7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

Index: linux-2.6/drivers/md/md.c
===================================================================
--- linux-2.6.orig/drivers/md/md.c
+++ linux-2.6/drivers/md/md.c
@@ -4889,6 +4889,7 @@ static void stop_sync_thread(struct mdde
 
 	mddev_unlock(mddev);
 
+retry:
 	set_bit(MD_RECOVERY_INTR, &mddev->recovery);
 	/*
 	 * Thread might be blocked waiting for metadata update which will now
@@ -4898,9 +4899,11 @@ static void stop_sync_thread(struct mdde
 	if (work_pending(&mddev->sync_work))
 		flush_work(&mddev->sync_work);
 
-	wait_event(resync_wait,
+	if (!wait_event_timeout(resync_wait,
 		   !test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) ||
-		   (check_seq && sync_seq != atomic_read(&mddev->sync_seq)));
+		   (check_seq && sync_seq != atomic_read(&mddev->sync_seq)),
+		   HZ / 10))
+		goto retry;
 
 	if (locked)
 		mddev_lock_nointr(mddev);


  parent reply	other threads:[~2024-01-17 18:18 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 ` Mikulas Patocka [this message]
2024-01-18  1:32   ` [PATCH 2/7] md: fix a race condition when stopping the sync thread 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 ` [PATCH 3/7] md: test for MD_RECOVERY_DONE in stop_sync_thread Mikulas Patocka
2024-01-18  0:19   ` 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=8fb335e-6d2c-dbb5-d7-ded8db5145a@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