From: Eric Dumazet <eric.dumazet@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jens Rosenboom <jens@mcbone.net>, 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: Mon, 27 Jul 2009 15:41:56 +0200 [thread overview]
Message-ID: <4A6DAEA4.9090107@gmail.com> (raw)
In-Reply-To: <1248701812.6987.1637.camel@twins>
Peter Zijlstra a écrit :
> On Mon, 2009-07-27 at 14:45 +0200, Jens Rosenboom wrote:
>
>> Good question, but as this happens on a production machine, I cannot
>> easily change the installation to check this.
>
> Uhm, but you do run .31-rc4 on it? :-)
>
>> Attaching an strace to the process gives just
>>
>> # strace -p 12886
>> Process 12886 attached - interrupt to quit
>>
>> and nothing further.
>
> Bugger.. how easy it is to reproduce?
> --
Strange thing is that "ps ax" doesnt use threads at all.
Stack trace seems to show mm_release() calls futex code,
but this part should not be called when a mono threaded program
exits (its clear_child_tid should be NULL at this point)
next prev parent reply other threads:[~2009-07-27 13:42 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 [this message]
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
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=4A6DAEA4.9090107@gmail.com \
--to=eric.dumazet@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.