From: Junaid Shahid <junaids@google.com>
To: linux-kernel@vger.kernel.org
Cc: andreslc@google.com, gthelen@google.com, rusty@rustcorp.com.au
Subject: [PATCH] kthread: Fix race condition between kthread_parkme() and kthread_unpark()
Date: Fri, 28 Apr 2017 19:32:36 -0700 [thread overview]
Message-ID: <20170429023236.60452-1-junaids@google.com> (raw)
In general, if kthread_unpark() and kthread_parkme() execute together,
the kthread is supposed to be in an unparked state. This is because
kthread_unpark() either wakes up the thread if it already got parked,
or it cancels a prior kthread_park() call and hence renders the
kthread_parkme() moot.
However, if kthread_unpark() happens to execute between the time that
kthread_parkme() checks the KTHREAD_SHOULD_STOP flag and sets the
KTHREAD_IS_PARKED flag, then kthread_unpark() will not wake up the
thread and it will remain in a parked state.
This is fixed by making the checking of KTHREAD_SHOULD_STOP and the
setting of KTHREAD_IS_PARKED atomic via a cmpxchg inside kthread_parkme.
Signed-off-by: Junaid Shahid <junaids@google.com>
---
kernel/kthread.c | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/kernel/kthread.c b/kernel/kthread.c
index 26db528c1d88..651f03baf62f 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -169,12 +169,20 @@ void *kthread_probe_data(struct task_struct *task)
static void __kthread_parkme(struct kthread *self)
{
+ ulong flags;
+
__set_current_state(TASK_PARKED);
- while (test_bit(KTHREAD_SHOULD_PARK, &self->flags)) {
- if (!test_and_set_bit(KTHREAD_IS_PARKED, &self->flags))
- complete(&self->parked);
- schedule();
+ flags = self->flags;
+
+ while (test_bit(KTHREAD_SHOULD_PARK, &flags)) {
+ if (cmpxchg(&self->flags, flags,
+ flags | (1 << KTHREAD_IS_PARKED)) == flags) {
+ if (!test_bit(KTHREAD_IS_PARKED, &flags))
+ complete(&self->parked);
+ schedule();
+ }
__set_current_state(TASK_PARKED);
+ flags = self->flags;
}
clear_bit(KTHREAD_IS_PARKED, &self->flags);
__set_current_state(TASK_RUNNING);
--
2.13.0.rc0.306.g87b477812d-goog
next reply other threads:[~2017-04-29 2:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 2:32 Junaid Shahid [this message]
2017-05-30 22:37 ` [PATCH] kthread: Fix race condition between kthread_parkme() and kthread_unpark() Junaid Shahid
2017-05-30 22:40 ` Andrew Morton
2017-07-18 0:13 ` Junaid Shahid
2017-07-18 6:35 ` Thomas Gleixner
2017-09-27 12:17 ` Peter Zijlstra
[not found] ` <CAL-GctE0BLVk=ps09dnir8pcpnfzg88jMK4CKkRVmY7-ho87nQ@mail.gmail.com>
2017-09-29 7:59 ` Thomas Gleixner
2017-09-29 8:28 ` Peter Zijlstra
2017-09-29 20:58 ` Junaid Shahid
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=20170429023236.60452-1-junaids@google.com \
--to=junaids@google.com \
--cc=andreslc@google.com \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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