From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Subject: Re: [GIT PULL] SLAB include file dependency fixes + kmemtrace updates
Date: Mon, 6 Apr 2009 18:51:10 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904061842490.4010@localhost.localdomain> (raw)
In-Reply-To: <20090405193944.GA12691@elte.hu>
On Sun, 5 Apr 2009, Ingo Molnar wrote:
>
> Please pull the latest kmemtrace-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git kmemtrace-for-linus
>
> We kept this topic separate from the main tracing tree due to the
> unexpectedly wide and messy-looking scope of the fixes Pekka needed
> to do to untangle various slab*.h, rcu*.h and fs.h dependency
> chains.
I'm not sure this is the tree that brings in the problem, but my wife's
Mac Mini won't boot any more, and it looks like some slub or percpu issue,
so regardless, roughly the right people are involved in the cc here
already.
I get odd NUL page faults or GP faults in either __kmalloc,
__kmalloc_track_caller or kmem_cache_alloc, and they all seem to happen on
roughly the same code, ie it's something like this:
movq 752(%r13,%rax,8), %rdx # <variable>.cpu_slab, c
movl 24(%rdx), %eax # <variable>.objsize,
movl %eax, -44(%rbp) #, objsize
movq (%rdx), %r12 # <variable>.freelist, object
testq %r12, %r12 # object
je .L617 #,
mov 20(%rdx), %eax # <variable>.offset, <variable>.offset
-> movq (%r12,%rax,8), %rax #* object, tmp79
movq %rax, (%rdx) # tmp79, <variable>.freelist
where that arrow points to the instruction that seems to be faulting.
I think it's this code:
object = c->freelist;
c->freelist = object[c->offset];
and that "object[c->offset]" in particular.
I have not tried to bisect it yet, and I'll do that, but if this sounds
familiar to anybody, please holler before I waste a lot of time on it.
Linus
next prev parent reply other threads:[~2009-04-07 1:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 19:39 [GIT PULL] SLAB include file dependency fixes + kmemtrace updates Ingo Molnar
2009-04-05 19:56 ` Linus Torvalds
2009-04-05 20:02 ` Linus Torvalds
2009-04-07 1:51 ` Linus Torvalds [this message]
2009-04-07 3:51 ` Linus Torvalds
2009-04-07 4:20 ` Linus Torvalds
2009-04-07 4:45 ` Linus Torvalds
2009-04-07 5:02 ` Wu Fengguang
2009-04-07 5:28 ` [patch] ramfs: add support for "mode=" mount option, fix Ingo Molnar
2009-04-07 5:55 ` Wu Fengguang
2009-04-07 6:03 ` Ingo Molnar
2009-04-07 6:16 ` [PATCH] ramfs: fix double freeing s_fs_info on failed mount Wu Fengguang
2009-04-07 6:53 ` Ingo Molnar
2009-04-07 7:05 ` Wu Fengguang
2009-04-07 6:20 ` [PATCH] ramfs: add support for "mode=" mount option, fix Ingo Molnar
2009-04-07 5:30 ` [GIT PULL] SLAB include file dependency fixes + kmemtrace updates Wu Fengguang
2009-04-07 4:58 ` Ingo Molnar
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=alpine.LFD.2.00.0904061842490.4010@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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