From: Pekka Pietikainen <pp@ee.oulu.fi>
To: marcel@holtmann.org
Cc: netdev@vger.kernel.org
Subject: [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue
Date: Sun, 17 Sep 2006 14:36:46 +0300 [thread overview]
Message-ID: <20060917113646.GA27178@ee.oulu.fi> (raw)
Hiya!
Got this from a 2.6.18rc7-based fedora-devel kernel:
=============================================
[ INFO: possible recursive locking detected ]
2.6.17-1.2647.fc6 #1
---------------------------------------------
sdpd/4955 is trying to acquire lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [<f0cea241>] bt_accept_dequeue+0x26/0xc6 [bluetooth]
but task is already holding lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [<f0b90088>] l2cap_sock_accept+0x41/0x11e [l2cap]
other info that might help us debug this:
1 lock held by sdpd/4955:
#0: (sk_lock-AF_BLUETOOTH){--..}, at: [<f0b90088>] l2cap_sock_accept+0x41/0x11e [l2cap]
stack backtrace:
[<c04051ee>] show_trace_log_lvl+0x58/0x171
[<c0405802>] show_trace+0xd/0x10
[<c040591b>] dump_stack+0x19/0x1b
[<c043b9e1>] __lock_acquire+0x778/0x99c
[<c043c176>] lock_acquire+0x4b/0x6d
[<c05b27e3>] lock_sock+0xac/0xbc
[<f0cea241>] bt_accept_dequeue+0x26/0xc6 [bluetooth]
[<f0b90129>] l2cap_sock_accept+0xe2/0x11e [l2cap]
[<c05b1bd7>] sys_accept+0xd8/0x179
[<c05b1d1f>] sys_socketcall+0xa7/0x186
[<c0403faf>] syscall_call+0x7/0xb
DWARF2 unwinder stuck at syscall_call+0x7/0xb
Leftover inexact backtrace:
[<c0405802>] show_trace+0xd/0x10
[<c040591b>] dump_stack+0x19/0x1b
[<c043b9e1>] __lock_acquire+0x778/0x99c
[<c043c176>] lock_acquire+0x4b/0x6d
[<c05b27e3>] lock_sock+0xac/0xbc
[<f0cea241>] bt_accept_dequeue+0x26/0xc6 [bluetooth]
[<f0b90129>] l2cap_sock_accept+0xe2/0x11e [l2cap]
[<c05b1bd7>] sys_accept+0xd8/0x179
[<c05b1d1f>] sys_socketcall+0xa7/0x186
[<c0403faf>] syscall_call+0x7/0xb
next reply other threads:[~2006-09-17 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 11:36 Pekka Pietikainen [this message]
2006-09-17 12:18 ` [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue Marcel Holtmann
2006-09-17 18:32 ` Pekka Pietikainen
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=20060917113646.GA27178@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--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;
as well as URLs for NNTP newsgroup(s).