From: Ray Lee <ray-lk@madrabbit.org>
To: Jens Rosenboom <jens.rosenboom@freenet.ag>
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: Mon, 27 Jul 2009 09:00:44 -0700 [thread overview]
Message-ID: <2c0942db0907270900uef8f32ao72319090d816d3c4@mail.gmail.com> (raw)
In-Reply-To: <20090727140039.GC13577@bo.mcbone.net>
On Mon, Jul 27, 2009 at 7:00 AM, Jens Rosenboom
<jens.rosenboom@freenet.ag> wrote:
>
> On Mon, Jul 27, 2009 at 03:36:52PM +0200, Peter Zijlstra wrote:
> > 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? :-)
>
> In the hope of verifying a patch, yes. Before that we had 2.6.29.4
> for some time.
In principle you should be able to run an x86_64 kernel on that
machine with the 32-bit userspace unchanged. The only hassle would be
if you are using any kernel modules outside the normal tree. So, no
need to change the full installation.
next prev parent reply other threads:[~2009-07-27 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 8:00 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 [this message]
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=2c0942db0907270900uef8f32ao72319090d816d3c4@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=jens.rosenboom@freenet.ag \
--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
all inboxes | Powered by JetHome®