From: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
To: linux-rt-users@vger.kernel.org
Subject: [4.4.4-rt11] Possiblie recursive locking detected in kswapd / mb_cache_shrink_scan()
Date: Mon, 14 Mar 2016 18:00:58 -0300 [thread overview]
Message-ID: <20160314210058.GE29798@uudg.org> (raw)
Hello,
I just started using 4.4.4-rt11 this afternoon and saw the lockdep splat below.
Is this something new or did I miss a patch floating on the list?
[67547.917898] =============================================
[67547.917898] [ INFO: possible recursive locking detected ]
[67547.917900] 4.4.4-rt11 #4 Not tainted
[67547.917900] ---------------------------------------------
[67547.917901] kswapd0/59 is trying to acquire lock:
[67547.917908] (&h->lock#2){+.+.-.}, at: [<ffffffff812934dc>] mb_cache_shrink_scan+0xac/0x220
[67547.917908]
but task is already holding lock:
[67547.917910] (&h->lock#2){+.+.-.}, at: [<ffffffff812934ca>] mb_cache_shrink_scan+0x9a/0x220
[67547.917911]
other info that might help us debug this:
[67547.917911] Possible unsafe locking scenario:
[67547.917911] CPU0
[67547.917911] ----
[67547.917912] lock(&h->lock#2);
[67547.917913] lock(&h->lock#2);
[67547.917913]
*** DEADLOCK ***
[67547.917913] May be due to missing lock nesting notation
[67547.917914] 2 locks held by kswapd0/59:
[67547.917917] #0: (shrinker_rwsem){+.+...}, at: [<ffffffff810e77d2>] rt_down_read_trylock+0x22/0x30
[67547.917919] #1: (&h->lock#2){+.+.-.}, at: [<ffffffff812934ca>] mb_cache_shrink_scan+0x9a/0x220
[67547.917920]
stack backtrace:
[67547.917921] CPU: 0 PID: 59 Comm: kswapd0 Not tainted 4.4.4-rt11 #4
[67547.917922] Hardware name: Hewlett-Packard p7-1512/2ADA, BIOS 8.15 02/05/2013
[67547.917923] 0000000000000086 000000005fca2e71 ffff88018a9fba10 ffffffff813d5412
[67547.917925] ffffffff828ede50 ffff88018a9f4000 ffff88018a9fbb00 ffffffff810e0d66
[67547.917926] ffff88018a9fbb08 000000000000008a ffffffff828e58a0 ffffffff81c0bf18
[67547.917926] Call Trace:
[67547.917929] [<ffffffff813d5412>] dump_stack+0x67/0x95
[67547.917931] [<ffffffff810e0d66>] __lock_acquire+0x1cf6/0x1d30
[67547.917934] [<ffffffff813f55d7>] ? debug_smp_processor_id+0x17/0x20
[67547.917936] [<ffffffff810deb49>] ? mark_held_locks+0x79/0xa0
[67547.917940] [<ffffffff817dc0cc>] ? _raw_spin_unlock_irqrestore+0x6c/0x80
[67547.917941] [<ffffffff810e1907>] lock_acquire+0xf7/0x240
[67547.917942] [<ffffffff812934dc>] ? mb_cache_shrink_scan+0xac/0x220
[67547.917944] [<ffffffff817dbb11>] _raw_spin_lock+0x41/0x80
[67547.917945] [<ffffffff812934dc>] ? mb_cache_shrink_scan+0xac/0x220
[67547.917946] [<ffffffff812934dc>] mb_cache_shrink_scan+0xac/0x220
[67547.917949] [<ffffffff811bfaaa>] shrink_slab.part.41+0x24a/0x600
[67547.917951] [<ffffffff811c479a>] shrink_zone+0x2ca/0x2e0
[67547.917953] [<ffffffff811c5ee1>] kswapd+0x581/0xbc0
[67547.917955] [<ffffffff811c5960>] ? mem_cgroup_shrink_node_zone+0x3c0/0x3c0
[67547.917957] [<ffffffff810a9b71>] kthread+0x101/0x120
[67547.917959] [<ffffffff810a9a70>] ? kthread_create_on_node+0x250/0x250
[67547.917960] [<ffffffff817dcfff>] ret_from_fork+0x3f/0x70
[67547.917962] [<ffffffff810a9a70>] ? kthread_create_on_node+0x250/0x250
Best regards,
Luis
next reply other threads:[~2016-03-14 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 21:00 Luis Claudio R. Goncalves [this message]
2016-03-19 8:33 ` [4.4.4-rt11] Possiblie recursive locking detected in kswapd / mb_cache_shrink_scan() Thomas Gleixner
2016-03-21 13:34 ` Luis Claudio R. Goncalves
2016-03-21 14:40 ` Josh Cartwright
2016-03-21 20:47 ` Luis Claudio R. Goncalves
2016-03-29 15:04 ` Sebastian Andrzej Siewior
2016-03-29 18:20 ` Josh Cartwright
2016-03-29 23:14 ` Josh Cartwright
2016-03-30 8:16 ` Sebastian Andrzej Siewior
2016-03-31 5:04 ` [PATCH] list_bl: fixup bogus lockdep warning Josh Cartwright
2016-04-01 10:46 ` Sebastian Andrzej Siewior
2016-04-01 10:49 ` Sebastian Andrzej Siewior
2016-04-01 17:02 ` Josh Cartwright
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=20160314210058.GE29798@uudg.org \
--to=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
/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).