From: Pekka Enberg <penberg@cs.helsinki.fi>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
viro@zeniv.linux.org.uk, 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: Wed, 10 Mar 2010 12:20:50 +0200 [thread overview]
Message-ID: <4B977282.40505@cs.helsinki.fi> (raw)
In-Reply-To: <2375c9f91003100029q7d64bbf7xce15eee97f7e2190@mail.gmail.com>
AmA(C)rico Wang kirjoitti:
> Hello, mm experts,
>
> I triggered an mm bug today, the full backtrace is here:
>
> http://pastebin.ca/1831436
>
> I am using yesterday's Linus tree.
>
> It's not easy to reproduce this, I got this very randomly.
>
> Some related config's are:
>
> CONFIG_SLAB=y
> CONFIG_SLABINFO=y
> # CONFIG_DEBUG_SLAB is not set
>
> Please let me know if you need more info.
Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
Anyway, it seems very unlikely that it's caused by the SLAB changes in
-rc1 so I'm CC'ing scheduler and fs folks in case the oops rings a bell.
Pekka
--
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>
next prev parent reply other threads:[~2010-03-10 10:20 UTC|newest]
Thread overview: 7+ 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 10:20 ` Pekka Enberg [this message]
2010-03-10 14:33 ` Christoph Lameter
2010-03-11 2:42 ` Américo Wang
2010-03-11 9:57 ` Américo Wang
2010-03-11 10:49 ` Pekka Enberg
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=4B977282.40505@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--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=peterz@infradead.org \
--cc=roland@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xiyou.wangcong@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;
as well as URLs for NNTP newsgroup(s).