From: Thomas Gleixner <tglx@linutronix.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
alokk@calsoftinc.com
Subject: Re: [BUG] Lockdep recursive locking in kmem_cache_free
Date: Fri, 28 Jul 2006 22:11:41 +0200 [thread overview]
Message-ID: <1154117501.10196.2.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0607280833510.18635@schroedinger.engr.sgi.com>
On Fri, 2006-07-28 at 08:35 -0700, Christoph Lameter wrote:
> On Fri, 28 Jul 2006, Thomas Gleixner wrote:
>
> > If you need more info, I can add debugs. It happens every bootup.
>
> Could you tell me why _spin_lock and _spin_unlock seem
> to be calling into the slab allocator? Also what is child_rip()? Cannot
> find that function upstream.
arch/x86_64/kernel/entry.S
child_rip:
/*
* Here we are in the child and the registers are set as they were
* at kernel_thread() invocation in the parent.
*/
movq %rdi, %rax
movq %rsi, %rdi
call *%rax
# exit
xorl %edi, %edi
call do_exit
ENDPROC(child_rip)
tglx
next prev parent reply other threads:[~2006-07-28 20:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 23:56 [BUG] Lockdep recursive locking in kmem_cache_free Thomas Gleixner
2006-07-28 5:22 ` Pekka Enberg
2006-07-28 6:14 ` Thomas Gleixner
2006-07-28 15:35 ` Christoph Lameter
2006-07-28 20:11 ` Thomas Gleixner [this message]
2006-07-28 20:18 ` Christoph Lameter
2006-07-28 20:27 ` Arjan van de Ven
2006-07-28 20:27 ` Thomas Gleixner
2006-07-28 20:35 ` Thomas Gleixner
2006-07-28 20:36 ` Christoph Lameter
2006-07-28 20:47 ` Thomas Gleixner
2006-07-28 20:48 ` Christoph Lameter
2006-07-28 21:12 ` Ravikiran G Thirumalai
2006-07-28 21:20 ` Thomas Gleixner
2006-08-02 19:10 ` Ravikiran G Thirumalai
2006-08-07 7:27 ` Thomas Gleixner
2006-07-28 21:26 ` Christoph Lameter
2006-07-28 21:34 ` Alok Kataria
2006-07-29 4:26 ` Ravikiran G Thirumalai
2006-07-28 14:53 ` Christoph Lameter
2006-07-28 17:11 ` Ravikiran G Thirumalai
2006-07-28 17:14 ` Arjan van de Ven
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=1154117501.10196.2.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=alokk@calsoftinc.com \
--cc=arjan@infradead.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/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