From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-mm <linux-mm@kvack.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] SLOB's krealloc() seems bust
Date: Tue, 07 Oct 2008 15:57:20 +0200 [thread overview]
Message-ID: <1223387841.26330.36.camel@lappy.programming.kicks-ass.net> (raw)
My test box would crash 50% of the bootups like so:
[ 12.002323] BUG: unable to handle kernel paging request at ffff88047bdd513c
[ 12.003310] IP: [<ffffffff80261f17>] load_module+0x6c8/0x1b2a
[ 12.003310] PGD 202063 PUD 0
[ 12.003310] Oops: 0000 [1] PREEMPT SMP
[ 12.003310] CPU 0
[ 12.003310] Modules linked in: kvm_amd kvm sg sr_mod serio_raw k8temp floppy pcspkr button cdrom shpchp
[ 12.003310] Pid: 1219, comm: modprobe Not tainted 2.6.27-rc9 #452
Which points us to the percpu_modalloc() code.
After adding some printk's to get some insight into the matter I got the
following:
[ 10.058055] percpu_modalloc: pcpu_size: ffff88007d82c0e8 size: 8 align: 8 name: kvm_amd
[ 10.066042] percpu_modalloc: pcpu_size[0] = -37536 ptr: ffffffff80757000 extra: 0
[ 10.073505] percpu_modalloc: pcpu_size[1] = 8192 ptr: ffffffff807602a0 extra: 0
[ 10.080795] split_block: pcpu_size: ffff88007d82c0e8 i: 1 size: 8
[ 10.086875] split_block: pcpu_size: ffff88007bdd5140
[ 10.091828] split_block: pcpu_size[0] = 2078109024
[ 10.096607] split_block: pcpu_size[1] = -30720
[ 10.101039] split_block: pcpu_size[0] = 2078109024
[ 10.105817] split_block: pcpu_size[1] = -30720
[ 10.110249] split_block: pcpu_size[2] = -30720
[ 10.114682] split_block: pcpu_size[1] = 8 pcpu_size[2] = -30728
Which basically shows us that the content of the pcpu_size[] array got
corrupted after the krealloc() call in split_block().
Which made me look at which slab allocator I had selected, which turned
out to be SLOB (from testing the network swap stuff).
Flipping it back to SLUB seems to cure the issue...
Will put poking at SLOB on the todo list somewhere, feel free to beat me
to it ;-)
--
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 reply other threads:[~2008-10-07 13:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 13:57 Peter Zijlstra [this message]
2008-10-07 14:07 ` Christoph Lameter
2008-10-07 14:13 ` Peter Zijlstra
2008-10-07 14:26 ` Christoph Lameter
2008-10-07 15:00 ` Matt Mackall
2008-10-07 15:20 ` Christoph Lameter
2008-10-07 15:58 ` Matt Mackall
2008-10-07 16:10 ` Peter Zijlstra
2008-10-07 16:37 ` Linus Torvalds
2008-10-07 16:37 ` Matt Mackall
2008-10-07 16:57 ` Pekka Enberg
2008-10-07 17:13 ` Matt Mackall
2008-10-07 17:31 ` Pekka Enberg
2008-10-07 23:08 ` Matt Mackall
2008-10-08 4:22 ` Nick Piggin
2008-10-08 4:46 ` Matt Mackall
2008-10-08 4:54 ` Nick Piggin
2008-10-08 5:11 ` Nick Piggin
2008-10-08 5:15 ` Matt Mackall
2008-10-08 6:43 ` Peter Zijlstra
2008-10-08 7:25 ` Pekka Enberg
2008-10-08 7:37 ` Peter Zijlstra
2008-10-08 7:39 ` Pekka Enberg
2008-10-07 17:57 ` Linus Torvalds
2008-10-07 18:11 ` Peter Zijlstra
2008-10-07 18:18 ` Linus Torvalds
2008-10-08 19:51 ` Matt Mackall
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=1223387841.26330.36.camel@lappy.programming.kicks-ass.net \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=nickpiggin@yahoo.com.au \
--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