From: Jakub Jelinek <jakub@redhat.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Andrew Morton <akpm@osdl.org>, Jamie Lokier <jamie@shareable.org>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
Chris Morgan <cmorgan@alum.wpi.edu>,
paul@linuxaudiosystems.com, seto.hidetoshi@jp.fujitsu.com
Subject: Re: kernel bug: futex_wait hang
Date: Tue, 22 Mar 2005 01:34:05 -0500 [thread overview]
Message-ID: <20050322063405.GN32746@devserv.devel.redhat.com> (raw)
In-Reply-To: <1111469453.3563.0.camel@mindpipe>
On Tue, Mar 22, 2005 at 12:30:53AM -0500, Lee Revell wrote:
> On Mon, 2005-03-21 at 21:08 -0800, Andrew Morton wrote:
> > Jamie Lokier <jamie@shareable.org> wrote:
> > >
> > > The most recent messages under "Futex queue_me/get_user ordering",
> > > with a patch from Jakub Jelinek will fix this problem by changing the
> > > kernel. Yes, you should apply Jakub's most recent patch, message-ID
> > > "<20050318165326.GB32746@devserv.devel.redhat.com>".
> > >
> > > I have not tested the patch, but it looks convincing.
> >
> > OK, thanks. Lee && Paul, that's at
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm1/broken-out/futex-queue_me-get_user-ordering-fix.patch
> >
>
> Does not fix the problem.
Have you analyzed the use of mutexes/condvars in the program?
The primary suspect is a deadlock, race of some kind or other bug
in the program. All these will show up as a hang in FUTEX_WAIT.
The argument that it works with LinuxThreads doesn't count,
the timing and internals of both threading libraries are so different
that a program bug can only show up with one of the threading libraries
and not both.
Only once you distill a minimal self-contained testcase that proves
the program is correct and it gets analyzed, it is time to talk about
NPTL or kernel bugs.
Jakub
next prev parent reply other threads:[~2005-03-22 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 3:59 kernel bug: futex_wait hang Lee Revell
2005-03-22 4:20 ` Andrew Morton
2005-03-22 4:25 ` Lee Revell
2005-03-22 4:46 ` Jamie Lokier
2005-03-22 4:48 ` Jamie Lokier
2005-03-22 5:08 ` Andrew Morton
2005-03-22 5:30 ` Lee Revell
2005-03-22 6:34 ` Jakub Jelinek [this message]
2005-03-22 23:58 ` Lee Revell
2005-03-23 13:12 ` paul
2005-03-23 13:43 ` Jakub Jelinek
2005-03-22 5:15 ` Lee Revell
2005-03-22 15:30 ` Jamie Lokier
2005-03-22 23:18 ` Lee Revell
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=20050322063405.GN32746@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=akpm@osdl.org \
--cc=cmorgan@alum.wpi.edu \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul@linuxaudiosystems.com \
--cc=rlrevell@joe-job.com \
--cc=seto.hidetoshi@jp.fujitsu.com \
/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