From: Jan Stancek <jstancek@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: jstancek@redhat.com, srikar@linux.vnet.ibm.com, davidlohr@hp.com,
torvalds@linux-foundation.org, mingo@kernel.org,
lwoodman@redhat.com
Subject: [PATCH] futex: avoid race between requeue and wake
Date: Tue, 8 Apr 2014 10:47:15 +0200 [thread overview]
Message-ID: <b60ab13f8ae8fea64591670b017f1fe697cce7c9.1396945474.git.jstancek@redhat.com> (raw)
pthread_cond_broadcast/4-1.c testcase from openposix testsuite (LTP)
occasionally fails, because some threads fail to wake up.
Testcase creates 5 threads, which are all waiting on same condition.
Main thread then calls pthread_cond_broadcast() without holding mutex,
which calls:
futex(uaddr1, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, uaddr2, ..)
This immediately wakes up single thread A, which unlocks mutex and
tries to wake up another thread:
futex(uaddr2, FUTEX_WAKE_PRIVATE, 1)
If thread A manages to call futex_wake() before any waiters are requeued
for uaddr2, no other thread is woken up.
This patch is re-introducing check removed by:
commit 11d4616bd07f38d496bd489ed8fad1dc4d928823
futex: revert back to the explicit waiter counting code
Taking hb->lock in this situation will ensure that thread A needs to wait
in futex_wake() until main thread finishes requeue operation.
Signed-off-by: Jan Stancek <jstancek@redhat.com>
---
kernel/futex.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/kernel/futex.c b/kernel/futex.c
index 67dacaf..5163899 100644
--- a/kernel/futex.c
+++ b/kernel/futex.c
@@ -284,7 +284,10 @@ static inline void hb_waiters_dec(struct futex_hash_bucket *hb)
static inline int hb_waiters_pending(struct futex_hash_bucket *hb)
{
#ifdef CONFIG_SMP
- return atomic_read(&hb->waiters);
+ if (spin_is_locked(&hb->lock))
+ return 1;
+ else
+ return atomic_read(&hb->waiters);
#else
return 1;
#endif
--
1.7.1
next reply other threads:[~2014-04-08 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 8:47 Jan Stancek [this message]
2014-04-08 16:20 ` Linus Torvalds
2014-04-08 17:03 ` Jan Stancek
2014-04-08 17:33 ` Linus Torvalds
2014-04-08 18:13 ` Peter Zijlstra
2014-04-08 18:53 ` Linus Torvalds
2014-04-08 21:02 ` Jan Stancek
2014-04-08 22:30 ` Linus Torvalds
2014-04-09 2:19 ` Davidlohr Bueso
2014-04-09 5:41 ` Peter Zijlstra
2014-04-09 5:51 ` Mike Galbraith
2014-04-09 11:46 ` Jan Stancek
2014-04-09 15:12 ` Linus Torvalds
2014-04-09 19:03 ` Davidlohr Bueso
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=b60ab13f8ae8fea64591670b017f1fe697cce7c9.1396945474.git.jstancek@redhat.com \
--to=jstancek@redhat.com \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=mingo@kernel.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®