From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Lameter <cl@gentwo.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Sitsofe Wheeler <sitsofe@yahoo.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, penberg@kernel.org,
mpm@selenic.com, linux-mm@kvack.org
Subject: Re: lockdep recursive locking detected (rcu_kthread / __cache_free)
Date: Mon, 03 Oct 2011 23:06:19 +0200 [thread overview]
Message-ID: <1317675980.9417.1.camel@twins> (raw)
In-Reply-To: <alpine.DEB.2.00.1110031540560.11713@router.home>
On Mon, 2011-10-03 at 15:46 -0500, Christoph Lameter wrote:
> On Mon, 3 Oct 2011, Paul E. McKenney wrote:
>
> > The first lock was acquired here in an RCU callback. The later lock that
> > lockdep complained about appears to have been acquired from a recursive
> > call to __cache_free(), with no help from RCU. This looks to me like
> > one of the issues that arise from the slab allocator using itself to
> > allocate slab metadata.
>
> Right. However, this is a false positive since the slab cache with
> the metadata is different from the slab caches with the slab data. The slab
> cache with the metadata does not use itself any metadata slab caches.
Sure, but we're supposed to have annotated that.. see
init_node_lock_keys()
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-10-03 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111003175322.GA26122@sucs.org>
2011-10-03 20:31 ` lockdep recursive locking detected (rcu_kthread / __cache_free) Paul E. McKenney
2011-10-03 20:46 ` Christoph Lameter
2011-10-03 21:06 ` Peter Zijlstra [this message]
2011-10-03 21:47 ` Paul E. McKenney
2011-10-04 14:28 ` Christoph Lameter
2011-10-04 14:40 ` Peter Zijlstra
2011-10-04 14:50 ` Christoph Lameter
2011-10-04 15:09 ` Peter Zijlstra
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=1317675980.9417.1.camel@twins \
--to=peterz@infradead.org \
--cc=cl@gentwo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=mpm@selenic.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@kernel.org \
--cc=sitsofe@yahoo.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).