From: Christoph Lameter <clameter@sgi.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: alokk@calsoftinc.com, tglx@linutronix.de,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [BUG] Lockdep recursive locking in kmem_cache_free
Date: Fri, 28 Jul 2006 07:53:56 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607280744530.18198@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <84144f020607272222o7b1d0270p997b8e3bf07e39e7@mail.gmail.com>
On Fri, 28 Jul 2006, Pekka Enberg wrote:
> > [ 57.976447] [<ffffffff802542fc>] __lock_acquire+0x8cc/0xcb0
> > [ 57.976562] [<ffffffff80254a02>] lock_acquire+0x52/0x70
> > [ 57.976675] [<ffffffff8028f201>] kmem_cache_free+0x141/0x210
> > [ 57.976790] [<ffffffff804a6b74>] _spin_lock+0x34/0x50
> > [ 57.976903] [<ffffffff8028f201>] kmem_cache_free+0x141/0x210
> > [ 57.977018] [<ffffffff8028f388>] slab_destroy+0xb8/0xf0
Huh? _spin_lock calls kmem_cache_free?
> cache_reap
> reap_alien (grabs l3->alien[node]->lock)
> __drain_alien_cache
> free_block
> slab_destroy (slab management off slab)
> kmem_cache_free
> __cache_free
> cache_free_alien (recursive attempt on l3->alien[node] lock)
>
> Christoph?
This should not happen. __drain_alien_cache frees node local elements
thus cache_free_alien should not be called. However, if the slab
management was allocated on a different node from the slab data then we
may have an issue. However, both slab managemnt and the slab data are
allocated on the same node (with alloc_pages_node() and kmalloc_node).
If something went wrong with kmalloc_node or alloc_pages_node (fallback?)
then we may have an issue. Guess we need to look into this some more.
Alok, have you thought about this issue before?
next prev parent reply other threads:[~2006-07-28 14:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 23:56 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
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 [this message]
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=Pine.LNX.4.64.0607280744530.18198@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=alokk@calsoftinc.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--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
all inboxes | Powered by JetHome®