All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
	"Christoph Lameter" <cl@linux-foundation.org>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
	viro@zeniv.linux.org.uk, "Ingo Molnar" <mingo@elte.hu>,
	akpm@linux-foundation.org, roland@redhat.com,
	peterz@infradead.org
Subject: Re: 2.6.34-rc1: kernel BUG at mm/slab.c:2989!
Date: Fri, 12 Mar 2010 00:19:05 +0800	[thread overview]
Message-ID: <20100311161905.GB3804@hack> (raw)
In-Reply-To: <4B98CAC0.5030009@cs.helsinki.fi>

On Thu, Mar 11, 2010 at 12:49:36PM +0200, Pekka Enberg wrote:
> Américo Wang kirjoitti:
>> On Thu, Mar 11, 2010 at 10:42 AM, Américo Wang <xiyou.wangcong@gmail.com> wrote:
>>> On Wed, Mar 10, 2010 at 10:33 PM, Christoph Lameter
>>> <cl@linux-foundation.org> wrote:
>>>> On Wed, 10 Mar 2010, Pekka Enberg wrote:
>>>>
>>>>>> Please let me know if you need more info.
>>>>> Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
>>>> Run SLUB with CONFIG_SLUB_DEBUG_ON or specify slub_debug on the kernel
>>>> command line to have all allocations checked.
>>>>
>>>>
>>> Ok, I will try it today.
>>
>> Sorry, I can't trigger it today, either with SLAB or SLUB.
>
> Is it the exact same version or is it a new git snapshot?

No, I did a git pull, but it looks like only some btrfs updates...


WARNING: multiple messages have this Message-ID (diff)
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
	"Christoph Lameter" <cl@linux-foundation.org>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
	viro@zeniv.linux.org.uk, "Ingo Molnar" <mingo@elte.hu>,
	akpm@linux-foundation.org, roland@redhat.com,
	peterz@infradead.org
Subject: Re: 2.6.34-rc1: kernel BUG at mm/slab.c:2989!
Date: Fri, 12 Mar 2010 00:19:05 +0800	[thread overview]
Message-ID: <20100311161905.GB3804@hack> (raw)
In-Reply-To: <4B98CAC0.5030009@cs.helsinki.fi>

On Thu, Mar 11, 2010 at 12:49:36PM +0200, Pekka Enberg wrote:
> AmA(C)rico Wang kirjoitti:
>> On Thu, Mar 11, 2010 at 10:42 AM, AmA(C)rico Wang <xiyou.wangcong@gmail.com> wrote:
>>> On Wed, Mar 10, 2010 at 10:33 PM, Christoph Lameter
>>> <cl@linux-foundation.org> wrote:
>>>> On Wed, 10 Mar 2010, Pekka Enberg wrote:
>>>>
>>>>>> Please let me know if you need more info.
>>>>> Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
>>>> Run SLUB with CONFIG_SLUB_DEBUG_ON or specify slub_debug on the kernel
>>>> command line to have all allocations checked.
>>>>
>>>>
>>> Ok, I will try it today.
>>
>> Sorry, I can't trigger it today, either with SLAB or SLUB.
>
> Is it the exact same version or is it a new git snapshot?

No, I did a git pull, but it looks like only some btrfs updates...

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-03-11 16:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  8:29 2.6.34-rc1: kernel BUG at mm/slab.c:2989! Américo Wang
2010-03-10  8:29 ` Américo Wang
2010-03-10 10:20 ` Pekka Enberg
2010-03-10 10:20   ` Pekka Enberg
2010-03-10 14:33   ` Christoph Lameter
2010-03-10 14:33     ` Christoph Lameter
2010-03-11  2:42     ` Américo Wang
2010-03-11  2:42       ` Américo Wang
2010-03-11  9:57       ` Américo Wang
2010-03-11  9:57         ` Américo Wang
2010-03-11 10:49         ` Pekka Enberg
2010-03-11 10:49           ` Pekka Enberg
2010-03-11 16:19           ` Américo Wang [this message]
2010-03-11 16:19             ` Américo Wang

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=20100311161905.GB3804@hack \
    --to=xiyou.wangcong@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --cc=peterz@infradead.org \
    --cc=roland@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.