From: Ingo Molnar <mingo@elte.hu>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Sripathi Kodi <sripathik@in.ibm.com>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Subject: Re: [RESEND] [BUG] futex_unlock_pi() hurts my brain and may cause application deadlock
Date: Mon, 6 Aug 2007 09:20:12 +0200 [thread overview]
Message-ID: <20070806072012.GF5359@elte.hu> (raw)
In-Reply-To: <1185926019.8850.198.camel@localhost>
* john stultz <johnstul@us.ibm.com> wrote:
> Hey Ingo,
> I sent this fix for this back in the 2.6.21-rt9 era, and I thought to
> picked it up, but I think it arrived amid some futex churn and
> apparently has been dropped or was just lost.
>
> Some of our testers have been reporting futex deadlocks and this fix
> resolves it, so I believe it to still be needed.
hmm ... so the many rounds of pi-futex fixes from Alexey and Thomas did
not resolve that deadlock?
Ingo
prev parent reply other threads:[~2007-08-06 7:21 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
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 [this message]
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=20070806072012.GF5359@elte.hu \
--to=mingo@elte.hu \
--cc=johnstul@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--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