From: Bruno Wolff III <bruno@wolff.to>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH] sched: Fix 32bit race
Date: Tue, 12 Jul 2011 07:34:10 -0500 [thread overview]
Message-ID: <20110712123410.GA9067@wolff.to> (raw)
In-Reply-To: <1310472434.14978.27.camel@twins>
On Tue, Jul 12, 2011 at 14:07:14 +0200,
Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> Ingo, can we get the below patch into sched/urgent and towards Linus
> before he cuts a release?
>
> I'm surprised there weren't more 32bit-smp doesn't boot for me
> complaints, either Bruno is a very 'lucky' man, or nobody is using 32bit
> kernels any more since he was hitting this quite reliably.
On two different machines. Both an Athlon MP and an old Xeon were hitting
this problem on every boot.
next prev parent reply other threads:[~2011-07-12 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 12:07 [PATCH] sched: Fix 32bit race Peter Zijlstra
2011-07-12 12:34 ` Bruno Wolff III [this message]
2011-07-12 20:09 ` Paul E. McKenney
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=20110712123410.GA9067@wolff.to \
--to=bruno@wolff.to \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/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