From: Eric Dumazet <dada1@cosmosbay.com>
To: Jens Rosenboom <jens@mcbone.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
Sonny Rao <sonnyrao@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: futexes: Still infinite loop in get_futex_key() in 2.6.31-rc4
Date: Wed, 29 Jul 2009 12:26:04 +0200 [thread overview]
Message-ID: <4A7023BC.6000109@cosmosbay.com> (raw)
In-Reply-To: <1248861443.6757.20.camel@fnki-nb00130>
Jens Rosenboom a écrit :
> On Wed, 2009-07-29 at 08:22 +0200, Jens Rosenboom wrote:
>> On Mon, 2009-07-27 at 15:36 +0200, Peter Zijlstra wrote:
>> [...]
>>> Bugger.. how easy it is to reproduce?
>> Okay, my colleague found the right combination of scripts, take the two
>> attached, run them both a couple of times in parallel for some hours,
>> and get a stuck ps. This happens both on an old 2.6.29.1 I happened to
>> still have on one machine as with 2.6.31-rc4. Both of them dual-core
>> Opterons as the original one. If you want further tracebacks or other
>> information, let me know.
>
> Forget about null.pl even, just run pees.pl twice and a top to watch it,
> has worked for me within less than an hour several times now.
>
Ah that makes sense now...
maybe execve() forgets to clear clear_child_tid
next prev parent reply other threads:[~2009-07-29 10:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 8:00 futexes: Still infinite loop in get_futex_key() in 2.6.31-rc4 Jens Rosenboom
2009-07-27 11:31 ` Peter Zijlstra
2009-07-27 12:16 ` Jens Rosenboom
2009-07-27 12:23 ` Peter Zijlstra
2009-07-27 12:45 ` Jens Rosenboom
2009-07-27 13:36 ` Peter Zijlstra
2009-07-27 13:41 ` Eric Dumazet
2009-07-27 14:00 ` Jens Rosenboom
2009-07-27 16:00 ` Ray Lee
2009-07-29 6:22 ` Jens Rosenboom
2009-07-29 9:57 ` Jens Rosenboom
2009-07-29 10:01 ` Peter Zijlstra
2009-07-29 10:26 ` Eric Dumazet [this message]
2009-07-29 10:56 ` Eric Dumazet
2009-07-29 14:29 ` Jens Rosenboom
2009-07-30 14:13 ` Jens Rosenboom
2009-07-31 10:00 ` [ PATCH] execve: must clear current->clear_child_tid Eric Dumazet
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=4A7023BC.6000109@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=jens@mcbone.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sonnyrao@us.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