From: Kyle McMartin <kyle@mcmartin.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: stable@kernel.org, Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Request for backport of [PARISC] futex: special case cmpxchg NULL in kernel space
Date: Tue, 15 Apr 2008 12:09:03 -0400 [thread overview]
Message-ID: <20080415160903.GD22873@phobos.i.cabal.ca> (raw)
In-Reply-To: <1208274312.3131.11.camel@localhost.localdomain>
On Tue, Apr 15, 2008 at 10:45:11AM -0500, James Bottomley wrote:
> This is a fix for a bug introduced by tglx into 2.6.25 which we fixed
> upstream. However, he also got it backported to stable, so now 2.6.24.4
> panics on boot on parisc. The attached is the fix.
>
The fix is fine, but it was misdiagnosed. The problem is actually that
swapper's *mm is unset. I switched it to if (!current->mm) in git,
but as usual I'm a slacker and haven't pushed it anywhere.
+1 for stable from me.
next prev parent reply other threads:[~2008-04-15 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 15:45 Request for backport of [PARISC] futex: special case cmpxchg NULL in kernel space James Bottomley
2008-04-15 16:09 ` Kyle McMartin [this message]
2008-04-17 0:29 ` patch parisc-futex-special-case-cmpxchg-null-in-kernel-space.patch queued to 2.6.24-stable tree chrisw
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=20080415160903.GD22873@phobos.i.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-parisc@vger.kernel.org \
--cc=stable@kernel.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