From: Shaohua Li <shli@kernel.org>
To: Guoqing Jiang <gqjiang@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] md: always set THREAD_WAKEUP and wake up wqueue if thread existed
Date: Sun, 8 Oct 2017 20:32:59 -0700 [thread overview]
Message-ID: <20171009033259.qwf4mspwzgdmiqog@kernel.org> (raw)
In-Reply-To: <1507516368-6465-1-git-send-email-gqjiang@suse.com>
On Mon, Oct 09, 2017 at 10:32:48AM +0800, Guoqing Jiang wrote:
> Since commit 4ad23a976413 ("MD: use per-cpu counter for writes_pending"),
> the wait_queue is only got invoked if THREAD_WAKEUP is not set previously.
>
> With above change, I can see process_metadata_update could always hang on
> the wait queue, because mddev->thread could stay on 'D' status and the
> THREAD_WAKEUP flag is not cleared since there are lots of place to wake up
> mddev->thread. Then deadlock happened as follows:
>
> linux175:~ # ps aux|grep md|grep D
> root 20117 0.0 0.0 0 0 ? D 03:45 0:00 [md0_raid1]
> root 20125 0.0 0.0 0 0 ? D 03:45 0:00 [md0_cluster_rec]
> linux175:~ # cat /proc/20117/stack
> [<ffffffffa0635604>] dlm_lock_sync+0x94/0xd0 [md_cluster]
> [<ffffffffa0635674>] lock_token+0x34/0xd0 [md_cluster]
> [<ffffffffa0635804>] metadata_update_start+0x64/0x110 [md_cluster]
> [<ffffffffa04d985b>] md_update_sb.part.58+0x9b/0x860 [md_mod]
> [<ffffffffa04da035>] md_update_sb+0x15/0x30 [md_mod]
> [<ffffffffa04dc066>] md_check_recovery+0x266/0x490 [md_mod]
> [<ffffffffa06450e2>] raid1d+0x42/0x810 [raid1]
> [<ffffffffa04d2252>] md_thread+0x122/0x150 [md_mod]
> [<ffffffff81091741>] kthread+0x101/0x140
> linux175:~ # cat /proc/20125/stack
> [<ffffffffa0636679>] recv_daemon+0x3f9/0x5c0 [md_cluster]
> [<ffffffffa04d2252>] md_thread+0x122/0x150 [md_mod]
> [<ffffffff81091741>] kthread+0x101/0x140
>
> So let's revert the part of code in the commit to resovle the problem since
> we can't get lots of benefits of previous change.
>
> Fixes: 4ad23a976413 ("MD: use per-cpu counter for writes_pending")
> Signed-off-by: Guoqing Jiang <gqjiang@suse.com>
> ---
> drivers/md/md.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 8b2eb0f..707471e 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -7468,8 +7468,8 @@ void md_wakeup_thread(struct md_thread *thread)
> {
> if (thread) {
> pr_debug("md: waking up MD thread %s.\n", thread->tsk->comm);
> - if (!test_and_set_bit(THREAD_WAKEUP, &thread->flags))
> - wake_up(&thread->wqueue);
> + set_bit(THREAD_WAKEUP, &thread->flags);
> + wake_up(&thread->wqueue);
> }
> }
> EXPORT_SYMBOL(md_wakeup_thread);
Applied, thanks!
prev parent reply other threads:[~2017-10-09 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 2:32 [PATCH] md: always set THREAD_WAKEUP and wake up wqueue if thread existed Guoqing Jiang
2017-10-09 3:32 ` Shaohua Li [this message]
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=20171009033259.qwf4mspwzgdmiqog@kernel.org \
--to=shli@kernel.org \
--cc=gqjiang@suse.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).