From: Darren Hart <dvhltc@us.ibm.com>
To: dino@in.ibm.com
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Eric Dumazet <eric.dumazet@gmail.com>,
John Stultz <johnstul@linux.vnet.ibm.com>,
stable@kernel.org
Subject: Re: [patch -rt] Fix infinite loop with 2.6.31.4-rt14 V2
Date: Fri, 23 Oct 2009 13:41:12 -0700 [thread overview]
Message-ID: <4AE214E8.9020406@us.ibm.com> (raw)
In-Reply-To: <20091023200858.GA7011@in.ibm.com>
Dinakar Guniguntala wrote:
> Application threads calling futex_wait_requeue_pi run in an infinite loop
> in the kernel if the futex value changes during the call. The following
> patch fixes the problem.
The key bit here being that EAGAIN == EWOULDBLOCK - who thought that was
a good idea?
>
> Signed-off-by: Dinakar Guniguntala <dino@in.ibm.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Darren Hart <dvhltc@us.ibm.com>
Signed-off-by: Darren Hart <dvhltc@us.ibm.com>
Adding the usual CC list for futexes as well as stable:
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>
CC: Eric Dumazet <eric.dumazet@gmail.com>
CC: John Stultz <johnstul@us.ibm.com>
CC: stable@kernel.org
>
> ---
> kernel/futex.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> Index: linux-2.6.31.4-rt14-lbf-f1/kernel/futex.c
> ===================================================================
> --- linux-2.6.31.4-rt14-lbf-f1.orig/kernel/futex.c
> +++ linux-2.6.31.4-rt14-lbf-f1/kernel/futex.c
> @@ -2188,6 +2188,12 @@ retry:
> spin_lock(&hb->lock);
> ret = handle_early_requeue_pi_wakeup(hb, &q, &key2, to);
> spin_unlock(&hb->lock);
> + if (ret == -EAGAIN) {
> + /* Retry on spurious wakeup */
> + put_futex_key(fshared, &q.key);
> + put_futex_key(fshared, &key2);
> + goto retry;
> + }
> if (ret)
> goto out_put_keys;
>
> @@ -2264,9 +2270,6 @@ out_put_keys:
> out_key2:
> put_futex_key(fshared, &key2);
>
> - /* Spurious wakeup ? */
> - if (ret == -EAGAIN)
> - goto retry;
> out:
> if (to) {
> hrtimer_cancel(&to->timer);
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
next prev parent reply other threads:[~2009-10-23 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 13:47 [patch -rt] Fix infinite loop with 2.6.31.4-rt14 Dinakar Guniguntala
2009-10-23 16:21 ` Darren Hart
2009-10-23 20:08 ` [patch -rt] Fix infinite loop with 2.6.31.4-rt14 V2 Dinakar Guniguntala
2009-10-23 20:41 ` Darren Hart [this message]
2009-10-23 23:29 ` Darren Hart
2009-10-26 19:01 ` Darren Hart
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=4AE214E8.9020406@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=dino@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=johnstul@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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).