From: Xiao Ni <xni@redhat.com>
To: song@kernel.org
Cc: yukuai3@huawei.com, linux-raid@vger.kernel.org
Subject: [PATCH RFC 1/1] md: Use pers->quiesce in mddev_suspend
Date: Tue, 5 Nov 2024 15:57:33 +0800 [thread overview]
Message-ID: <20241105075733.66101-1-xni@redhat.com> (raw)
One customer reports a bug: raid5 is hung when changing thread cnt
while resync is running. The stripes are all in conf->handle_list
and new threads can't handle them.
Commit b39f35ebe86d ("md: don't quiesce in mddev_suspend()") removes
pers->quiesce from mddev_suspend/resume, then we can't guarantee sync
requests finish in suspend operation. One personality knows itself the
best. So pers->quiesce is a proper way to let personality quiesce.
Fixes: b39f35ebe86d ("md: don't quiesce in mddev_suspend()")
Signed-off-by: Xiao Ni <xni@redhat.com>
---
drivers/md/md.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 67108c397c5a..7409ecb2df68 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -482,6 +482,9 @@ int mddev_suspend(struct mddev *mddev, bool interruptible)
return err;
}
+ if (mddev->pers)
+ mddev->pers->quiesce(mddev, 1);
+
/*
* For raid456, io might be waiting for reshape to make progress,
* allow new reshape to start while waiting for io to be done to
@@ -514,6 +517,9 @@ static void __mddev_resume(struct mddev *mddev, bool recovery_needed)
percpu_ref_resurrect(&mddev->active_io);
wake_up(&mddev->sb_wait);
+ if (mddev->pers)
+ mddev->pers->quiesce(mddev, 0);
+
if (recovery_needed)
set_bit(MD_RECOVERY_NEEDED, &mddev->recovery);
md_wakeup_thread(mddev->thread);
--
2.32.0 (Apple Git-132)
next reply other threads:[~2024-11-05 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 7:57 Xiao Ni [this message]
2024-11-05 8:14 ` [PATCH RFC 1/1] md: Use pers->quiesce in mddev_suspend Yu Kuai
2024-11-05 8:48 ` Xiao Ni
2024-11-05 8:16 ` Mariusz Tkaczyk
2024-11-05 8:29 ` Yu Kuai
2024-11-05 9:01 ` Xiao Ni
2024-11-05 9:22 ` Yu Kuai
2024-11-05 10:35 ` Xiao Ni
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=20241105075733.66101-1-xni@redhat.com \
--to=xni@redhat.com \
--cc=linux-raid@vger.kernel.org \
--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