From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm/recoverd: recheck kthread_should_stop() before schedule()
Date: Mon, 25 Sep 2017 14:07:28 -0500 [thread overview]
Message-ID: <20170925190728.GA16497@redhat.com> (raw)
In-Reply-To: <1506325670-1239-1-git-send-email-gqjiang@suse.com>
On Mon, Sep 25, 2017 at 03:47:50PM +0800, Guoqing Jiang wrote:
> Call schedule() here could make the thread miss wake
> up from kthread_stop(), so it is better to recheck
> kthread_should_stop() before call schedule(), a symptom
> happened when I run indefinite test (which mostly created
> clustered raid1, assemble it in other nodes, then stop
> them) of clustered raid.
Thanks, I put this into the next branch in linux-dlm (which I also
moved onto -rc2.)
prev parent reply other threads:[~2017-09-25 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 7:47 [Cluster-devel] [PATCH] dlm/recoverd: recheck kthread_should_stop() before schedule() Guoqing Jiang
2017-09-25 19:07 ` David Teigland [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=20170925190728.GA16497@redhat.com \
--to=teigland@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.