From: John Kacur <jkacur@redhat.com>
To: Nick Piggin <npiggin@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
john stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: lockdep "splat" on v2.6.33.5-rt23
Date: Thu, 24 Jun 2010 17:40:02 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1006241725550.22940@localhost.localdomain> (raw)
I believe this is related to the dcache scale discussion thread. I've
shown this to Peter privately, but thought it would be useful to share it
with everyone so we all have the same info.
The kernel is from tip/rt/2.6.33 up to commit
faf35813f204901f85dd0c6b3c5092e0064c6c2f
It has a lot of debug options enabled, but is not modified.
The "splat" is very easy to reproduce, it simply occurs when I
boot the kernel on my T500.
=============================================
[ INFO: possible recursive locking detected ]
2.6.33.5-rt23-tip-debug #3
---------------------------------------------
init/1 is trying to acquire lock:
(&dentry->d_lock/1){+.+...}, at: [<ffffffff811981be>]
shrink_dcache_parent+0x10f/0x2eb
but task is already holding lock:
(&dentry->d_lock/1){+.+...}, at: [<ffffffff811981be>]
shrink_dcache_parent+0x10f/0x2eb
other info that might help us debug this:
2 locks held by init/1:
#0: (&dentry->d_lock){+.+...}, at: [<ffffffff8119818e>]
shrink_dcache_parent+0xdf/0x2eb
#1: (&dentry->d_lock/1){+.+...}, at: [<ffffffff811981be>]
shrink_dcache_parent+0x10f/0x2eb
stack backtrace:
Pid: 1, comm: init Not tainted 2.6.33.5-rt23-tip-debug #3
Call Trace:
[<ffffffff810a68e2>] __lock_acquire+0xcb9/0xd35
[<ffffffff811981be>] ? shrink_dcache_parent+0x10f/0x2eb
[<ffffffff810a701c>] lock_acquire+0xd4/0xf1
[<ffffffff811981be>] ? shrink_dcache_parent+0x10f/0x2eb
[<ffffffff81521006>] rt_spin_lock_nested+0x3d/0x44
[<ffffffff811981be>] ? shrink_dcache_parent+0x10f/0x2eb
[<ffffffff81193456>] ? dentry_lru_del_init+0x3e/0xa8
[<ffffffff8119818e>] ? shrink_dcache_parent+0xdf/0x2eb
[<ffffffff811981be>] shrink_dcache_parent+0x10f/0x2eb
[<ffffffff811f59a4>] proc_flush_task+0xd4/0x26f
[<ffffffff81065ea7>] release_task+0x47/0x650
[<ffffffff81066e6a>] wait_consider_task+0x9ba/0x10b4
[<ffffffff810676e1>] do_wait+0x17d/0x38b
[<ffffffff810679e5>] sys_wait4+0xf6/0x119
[<ffffffff810037cc>] ? sysret_check+0x27/0x62
[<ffffffff810652a4>] ? child_wait_callback+0x0/0xa5
[<ffffffff8100379b>] system_call_fastpath+0x16/0x1b
[jkacur@tycho tip-rt-2.6.33]$ addr2line -e vmlinux ffffffff811981be
/home/jkacur/rt.linux.git/fs/dcache.c:1033
[jkacur@tycho tip-rt-2.6.33]$ addr2line -e vmlinux ffffffff8119818e
/home/jkacur/rt.linux.git/fs/dcache.c:1023
So that is function static int select_parent(struct dentry * parent)
line 1023 is
spin_lock(&this_parent->d_lock);
and lines 1032 and 1033 are
spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
dentry_lru_del_init(dentry);
If there is any other info I can provide to help solve this, or testing
etc, pls let me know!
John Kacur
next reply other threads:[~2010-06-24 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 15:40 John Kacur [this message]
2010-06-24 17:03 ` lockdep "splat" on v2.6.33.5-rt23 john stultz
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.LFD.2.00.1006241725550.22940@localhost.localdomain \
--to=jkacur@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=npiggin@suse.de \
--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