From: Pekka Enberg <penberg@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sebastian Siewior <sebastian@breakpoint.cc>,
Christoph Lameter <cl@linux-foundation.org>,
Matt Mackall <mpm@selenic.com>,
linux-mm@kvack.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: possible recursive locking detected cache_alloc_refill() + cache_flusharray()
Date: Wed, 20 Jul 2011 16:21:56 +0300 (EEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1107201619540.3528@tiger> (raw)
In-Reply-To: <alpine.LFD.2.02.1107172333340.2702@ionos>
On Sat, 16 Jul 2011, Sebastian Siewior wrote:
>> just hit the following with full debuging turned on:
>>
>> | =============================================
>> | [ INFO: possible recursive locking detected ]
>> | 3.0.0-rc7-00088-g1765a36 #64
>> | ---------------------------------------------
>> | udevd/1054 is trying to acquire lock:
>> | (&(&parent->list_lock)->rlock){..-...}, at: [<c00bf640>] cache_alloc_refill+0xac/0x868
>> |
>> | but task is already holding lock:
>> | (&(&parent->list_lock)->rlock){..-...}, at: [<c00be47c>] cache_flusharray+0x58/0x148
>> |
>> | other info that might help us debug this:
>> | Possible unsafe locking scenario:
>> |
>> | CPU0
>> | ----
>> | lock(&(&parent->list_lock)->rlock);
>> | lock(&(&parent->list_lock)->rlock);
On Sun, 17 Jul 2011, Thomas Gleixner wrote:
> Known problem. Pekka is looking into it.
Actually, I kinda was hoping Peter would make it go away. ;-)
Looking at the lockdep report, it's l3->list_lock and I really don't quite
understand why it started to happen now. There hasn't been any major
changes in mm/slab.c for a while. Did lockdep become more strict recently?
Pekka
--
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-07-20 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 21:18 Sebastian Siewior
2011-07-17 21:34 ` Thomas Gleixner
2011-07-20 13:21 ` Pekka Enberg [this message]
2011-07-20 13:30 ` Peter Zijlstra
2011-07-20 13:52 ` Pekka Enberg
2011-07-20 14:00 ` Christoph Lameter
2011-07-20 15:44 ` Peter Zijlstra
2011-07-21 7:14 ` Sebastian Siewior
2011-07-22 8:17 ` Pekka Enberg
2011-07-22 13:26 ` Peter Zijlstra
2011-07-23 11:22 ` Sebastian Andrzej Siewior
2011-07-28 10:46 ` Pekka Enberg
2011-07-28 10:56 ` Sebastian Andrzej Siewior
2011-07-28 10:56 ` Peter Zijlstra
2011-07-28 10:55 ` Pekka Enberg
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.DEB.2.00.1107201619540.3528@tiger \
--to=penberg@kernel.org \
--cc=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=peterz@infradead.org \
--cc=sebastian@breakpoint.cc \
--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