From: "Dave Young" <hidave.darkstar@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Netdev <netdev@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
David Miller <davem@davemloft.net>,
bluez-devel@lists.sf.net
Subject: bluetooth : lockdep warning on rfcomm
Date: Thu, 24 Jan 2008 11:02:55 +0800 [thread overview]
Message-ID: <a8e1da0801231902x5ab7691bq5a30e839f6c8cb71@mail.gmail.com> (raw)
=============================================
[ INFO: possible recursive locking detected ]
2.6.24-rc8-mm1 #8
---------------------------------------------
bluepush/3213 is trying to acquire lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [<f8978c80>]
l2cap_sock_bind+0x40/0x100 [l2cap]
but task is already holding lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [<f894a31e>]
rfcomm_sock_connect+0x3e/0xe0 [rfcomm]
other info that might help us debug this:
2 locks held by bluepush/3213:
#0: (sk_lock-AF_BLUETOOTH){--..}, at: [<f894a31e>]
rfcomm_sock_connect+0x3e/0xe0 [rfcomm]
#1: (rfcomm_mutex){--..}, at: [<f8947556>] rfcomm_dlc_open+0x26/0x60 [rfcomm]
stack backtrace:
Pid: 3213, comm: bluepush Not tainted 2.6.24-rc8-mm1 #8
[<c0132128>] ? printk+0x18/0x20
[<c0154437>] print_deadlock_bug+0xc7/0xe0
[<c01544bc>] check_deadlock+0x6c/0x80
[<c01548fc>] validate_chain+0x14c/0x320
[<c0156221>] __lock_acquire+0x1c1/0x730
[<c0156d89>] lock_acquire+0x79/0xb0
[<f8978c80>] ? l2cap_sock_bind+0x40/0x100 [l2cap]
[<c03c05f5>] lock_sock_nested+0x55/0x70
[<f8978c80>] ? l2cap_sock_bind+0x40/0x100 [l2cap]
[<f8978c80>] l2cap_sock_bind+0x40/0x100 [l2cap]
[<c03bdb4a>] kernel_bind+0xa/0x10
[<f8947afc>] rfcomm_session_create+0x4c/0x110 [rfcomm]
[<f8947509>] __rfcomm_dlc_open+0x129/0x150 [rfcomm]
[<f8947568>] rfcomm_dlc_open+0x38/0x60 [rfcomm]
[<f894a396>] rfcomm_sock_connect+0xb6/0xe0 [rfcomm]
[<c03bcd39>] sys_connect+0x99/0xd0
[<c010f509>] ? cache_add_dev+0x39/0x1a0
[<c015323d>] ? put_lock_stats+0xd/0x30
[<c01532c0>] ? lock_release_holdtime+0x60/0x80
[<c018e86c>] ? fget+0x7c/0x100
[<c0156b97>] ? __lock_release+0x47/0x70
[<c018e86c>] ? fget+0x7c/0x100
[<c02611b7>] ? copy_from_user+0x37/0x70
[<c03bd855>] sys_socketcall+0xa5/0x230
[<c0155659>] ? trace_hardirqs_on+0xb9/0x130
[<c010501b>] ? restore_nocheck+0x12/0x15
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next reply other threads:[~2008-01-24 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 3:02 Dave Young [this message]
2008-01-24 9:25 ` bluetooth : lockdep warning on rfcomm Dave Young
2008-01-25 5:37 ` Dave Young
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=a8e1da0801231902x5ab7691bq5a30e839f6c8cb71@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@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