From: Rusty Russell <rusty@rustcorp.com.au>
To: Hugh Dickins <hugh@veritas.com>
Cc: Jamie Lokier <jamie@shareable.org>
Cc: Klaus Dittrich <kladit@t-online.de>,
linux mailing-list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>, "Hu, Boris" <boris.hu@intel.com>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: 2.6.0-test6 oops futex"
Date: Wed, 01 Oct 2003 09:44:27 +1000 [thread overview]
Message-ID: <20031001054619.976472C105@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 30 Sep 2003 21:53:08 +0100." <Pine.LNX.4.44.0309302141220.4388-100000@localhost.localdomain>
In message <Pine.LNX.4.44.0309302141220.4388-100000@localhost.localdomain> you write:
> Consider unqueue_me on one cpu racing against this->key = key2 in
> futex_requeue on another. unqueue_me finds the right bh to lock
> from q->key, but futex_requeue is shifting q->key beneath it.
> Although futex_requeue holds both the relevant spinlocks, during
> reassignment of key an irrelevant hashqueue may get calculated
> and locked instead.
Yes, the lack of global lock does make this problematic. You end up
holding the lock on one queue and removing from another. I think the
recycling scenario a more likely cause in this case, but this too must
be fixed.
The clearest fix (other than going back to one big lock) is to have a
lock per futex to protect its contents (vs. the hash bucket lock which
protects the hash chain itself). But the following race-check is
sufficient (there are only two places where we call futex_hash on a
"live" futex):
Name: Futex Requeue Race
Author: Hugh Dickins, Typing by Rusty Russell
Status: Experimental
D: Consider unqueue_me on one cpu racing against this->key = key2 in
D: futex_requeue on another. unqueue_me finds the right bh to lock
D: from q->key, but futex_requeue is shifting q->key beneath it.
D: Although futex_requeue holds both the relevant spinlocks, during
D: reassignment of key an irrelevant hashqueue may get calculated
D: and locked instead.
diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal .26056-linux-2.6.0-test6-bk2/kernel/futex.c .26056-linux-2.6.0-test6-bk2.updated/kernel/futex.c
--- .26056-linux-2.6.0-test6-bk2/kernel/futex.c 2003-09-29 10:26:06.000000000 +1000
+++ .26056-linux-2.6.0-test6-bk2.updated/kernel/futex.c 2003-10-01 09:40:58.000000000 +1000
@@ -342,10 +342,19 @@ static inline void queue_me(struct futex
/* Return 1 if we were still queued (ie. 0 means we were woken) */
static inline int unqueue_me(struct futex_q *q)
{
- struct futex_hash_bucket *bh = hash_futex(&q->key);
+ struct futex_hash_bucket *bh;
+ union futex_key key;
int ret = 0;
+again:
+ key = q->key;
+ bh = hash_futex(&key);
spin_lock(&bh->lock);
+ if (unlikely(!match_futex(&key, q->key)) {
+ /* Race against futex_requeue */
+ spin_unlock(&bh_lock);
+ goto again;
+ }
if (!list_empty(&q->list)) {
list_del(&q->list);
ret = 1;
@@ -455,11 +464,20 @@ static unsigned int futex_poll(struct fi
struct poll_table_struct *wait)
{
struct futex_q *q = filp->private_data;
- struct futex_hash_bucket *bh = hash_futex(&q->key);
+ union futex_key key;
+ struct futex_hash_bucket *bh;
int ret = 0;
poll_wait(filp, &q->waiters, wait);
+again:
+ key = q->key;
+ bh = hash_futex(&key);
spin_lock(&bh->lock);
+ if (unlikely(!match_futex(&key, q->key)) {
+ /* Race against futex_requeue */
+ spin_unlock(&bh_lock);
+ goto again;
+ }
if (list_empty(&q->list))
ret = POLLIN | POLLRDNORM;
spin_unlock(&bh->lock);
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-10-01 5:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 9:23 2.6.0-test6 oops futex" Klaus Dittrich
2003-09-30 8:48 ` Jamie Lokier
2003-09-30 20:53 ` Hugh Dickins
2003-09-30 21:48 ` Ulrich Drepper
2003-09-30 23:44 ` Rusty Russell [this message]
2003-10-01 6:35 ` Jamie Lokier
2003-10-01 1:01 ` Jamie Lokier
2003-10-01 2:41 ` Jamie Lokier
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=20031001054619.976472C105@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=hugh@veritas.com \
--cc=jamie@shareable.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