From: Wu Fengguang <fengguang.wu@intel.com>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: recursive slqb_lock
Date: Thu, 26 Feb 2009 13:34:50 +0800 [thread overview]
Message-ID: <20090226053450.GA31108@localhost> (raw)
Hi Nick,
I got a lockdep warning. It looks like the slqb_lock will be taken
twice in the call chain:
s_start() => take slqb_lock
s_show()
gather_stats() => take slqb_lock again
Thanks,
Fengguang
---
[ 2229.013986] =============================================
[ 2229.017469] [ INFO: possible recursive locking detected ]
[ 2229.017469] 2.6.29-rc5-next-20090220 #57
[ 2229.017469] ---------------------------------------------
[ 2229.017469] mcookie/3167 is trying to acquire lock:
[ 2229.017469] (slqb_lock){+++++.}, at: [<ffffffff810d7960>] s_show+0x60/0x1f0
[ 2229.017469]
[ 2229.017469] but task is already holding lock:
[ 2229.017469] (slqb_lock){+++++.}, at: [<ffffffff810d7c09>] s_start+0x29/0xa0
[ 2229.017469]
[ 2229.017469] other info that might help us debug this:
[ 2229.017469] 2 locks held by mcookie/3167:
[ 2229.017469] #0: (&p->lock){+.+.+.}, at: [<ffffffff810fa79a>] seq_read+0x3a/0x3c0
[ 2229.017469] #1: (slqb_lock){+++++.}, at: [<ffffffff810d7c09>] s_start+0x29/0xa0
[ 2229.017469]
[ 2229.017469] stack backtrace:
[ 2229.017469] Pid: 3167, comm: mcookie Not tainted 2.6.29-rc5-next-20090220 #57
[ 2229.017469] Call Trace:
[ 2229.017469] [<ffffffff810705f0>] __lock_acquire+0xf90/0x1ad0
[ 2229.017469] [<ffffffff8106f605>] ? check_irq_usage+0xa5/0x100
[ 2229.017469] [<ffffffff8106c97c>] ? lockdep_init_map+0x4c/0x640
[ 2229.017469] [<ffffffff81071194>] lock_acquire+0x64/0x90
[ 2229.017469] [<ffffffff810d7960>] ? s_show+0x60/0x1f0
[ 2229.017469] [<ffffffff8149666b>] down_read+0x4b/0x80
[ 2229.017469] [<ffffffff810d7960>] ? s_show+0x60/0x1f0
[ 2229.017469] [<ffffffff810d7960>] s_show+0x60/0x1f0
[ 2229.017469] [<ffffffff810fa84b>] seq_read+0xeb/0x3c0
[ 2229.017469] [<ffffffff811ffead>] ? _raw_spin_unlock+0x7d/0xa0
[ 2229.017469] [<ffffffff810fa760>] ? seq_read+0x0/0x3c0
[ 2229.017469] [<ffffffff8111f469>] proc_reg_read+0x79/0xb0
[ 2229.017469] [<ffffffff810decc8>] vfs_read+0xc8/0x180
[ 2229.017469] [<ffffffff810dee70>] sys_read+0x50/0x90
[ 2229.017469] [<ffffffff8100c3f2>] system_call_fastpath+0x16/0x1b
next reply other threads:[~2009-02-26 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 5:34 Wu Fengguang [this message]
2009-03-01 15:07 ` recursive slqb_lock Nick Piggin
2009-03-01 17:00 ` Nick Piggin
2009-03-02 3:36 ` Wu Fengguang
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=20090226053450.GA31108@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.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