From: john stultz <johnstul@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Sripathi Kodi <sripathik@in.ibm.com>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [BUG] futex_unlock_pi() hurts my brain and may cause application deadlock
Date: Thu, 31 May 2007 07:50:27 -0700 [thread overview]
Message-ID: <1180623027.17878.2.camel@localhost> (raw)
In-Reply-To: <20070531142455.GA11310@elte.hu>
On Thu, 2007-05-31 at 16:24 +0200, Ingo Molnar wrote:
> * john stultz <johnstul@us.ibm.com> wrote:
>
> > So we've been seeing PI mutex deadlocks with a few of our
> > applications using the -rt kernel. After narrowing things down, we
> > were finding that the applications were indirectly calling
> > futex_unlock_pi(), which on occasion would return -EFAULT, which is
> > promptly ignored by glibc. This would cause the application to
> > continue on as if it has unlocked the mutex, until it tried to
> > reacquire it and deadlock.
>
> > --- a/kernel/futex.c
> > +++ b/kernel/futex.c
> > @@ -2011,6 +2011,7 @@ pi_faulted:
> > attempt);
> > if (ret)
> > goto out_unlock;
> > + uval = 0;
> > goto retry_locked;
>
> this looks good to me. Oleg has posted a few more fixes as well - have
> you tried those too?
Do you have a URL or subject line for the discussion?
I'll take a look and give them a whirl.
thanks
-john
next prev parent reply other threads:[~2007-05-31 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 0:49 [BUG] futex_unlock_pi() hurts my brain and may cause application deadlock john stultz
2007-05-31 1:29 ` Steven Rostedt
2007-05-31 14:53 ` Ulrich Drepper
2007-05-31 2:52 ` [PATCH RT] fix faulting bomb in futex_unlock_pi64 Steven Rostedt
2007-05-31 3:18 ` Steven Rostedt
2007-05-31 17:20 ` Ulrich Drepper
2007-05-31 14:24 ` [BUG] futex_unlock_pi() hurts my brain and may cause application deadlock Ingo Molnar
2007-05-31 14:50 ` john stultz [this message]
2007-05-31 14:55 ` Ingo Molnar
2007-05-31 16:48 ` john stultz
2007-07-31 23:53 ` [RESEND] " john stultz
2007-08-01 0:00 ` Steven Rostedt
2007-08-01 1:41 ` David Miller
2007-08-06 7:20 ` Ingo Molnar
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=1180623027.17878.2.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=rostedt@goodmis.org \
--cc=sripathik@in.ibm.com \
--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