public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Xiaotian Feng <xtfeng@gmail.com>, Greg Kroah-Hartman <gregkh@suse.de>
Cc: Miles Lane <miles.lane@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Cliff Wickman <cpw@sgi.com>,
	stable@kernel.org
Subject: Re: 2.6.35-rc3 -- kernel BUG at mm/vmalloc.c:216! - invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
Date: Thu, 24 Jun 2010 09:50:23 +0200	[thread overview]
Message-ID: <4C230E3F.4020107@gmail.com> (raw)
In-Reply-To: <AANLkTik5H_rQ2tPO6h3UtslOVzGQo-qoKW_YD8hULAA3@mail.gmail.com>

On 06/24/2010 09:45 AM, Xiaotian Feng wrote:
>> It's probably the same bug Cliff Wickman reported.
>> per_cpu_ptr_to_phys() was using wrong first chunk match logic which
>> ends up passing wrong addresses to vmalloc_to_page().  I have the
>> following fix patch queued in percpu#for-linus branch and was waiting
>> for Linus to come back.
>>
>>  http://git.kernel.org/?p=linux/kernel/git/tj/percpu.git;a=commitdiff_plain;h=9983b6f0cf8263e51bcf4c8a9dc0c1ef175b3c60;hp=a92d3ff9e5dbd958d8008a3e7a573e988e370ca3
>>
>> Can you please verify the above patch fixes the problem?
> 
> Yes, that patch fixes the problem on my box, thanks.

Thanks for verifying.  Greg, we'll have to wait till Linus comes back
for mainline but maybe it's a good idea to put this into -stable queue
early?  It's a rather straight forward bug fix and unlikely to be
contentious.

Thanks.

-- 
tejun

  reply	other threads:[~2010-06-24  7:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24  5:11 2.6.35-rc3 -- kernel BUG at mm/vmalloc.c:216! - invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC Miles Lane
2010-06-24  5:22 ` Xiaotian Feng
2010-06-24  7:15   ` Tejun Heo
2010-06-24  7:45     ` Xiaotian Feng
2010-06-24  7:50       ` Tejun Heo [this message]
2010-06-24 17:00         ` [stable] " Greg KH
2010-06-24  5:30 ` Xiaotian Feng
2010-06-24  5:50   ` Eric Dumazet
2010-06-25  3:27 ` Thomas Fjellstrom

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=4C230E3F.4020107@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cpw@sgi.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    --cc=stable@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xtfeng@gmail.com \
    /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