From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Pietikainen Subject: [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue Date: Sun, 17 Sep 2006 14:36:46 +0300 Message-ID: <20060917113646.GA27178@ee.oulu.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: netdev@vger.kernel.org Return-path: Received: from ee.oulu.fi ([130.231.61.23]:37302 "EHLO ee.oulu.fi") by vger.kernel.org with ESMTP id S964937AbWIQLg6 (ORCPT ); Sun, 17 Sep 2006 07:36:58 -0400 To: marcel@holtmann.org Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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: [] bt_accept_dequeue+0x26/0xc6 [bluetooth] but task is already holding lock: (sk_lock-AF_BLUETOOTH){--..}, at: [] 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: [] l2cap_sock_accept+0x41/0x11e [l2cap] stack backtrace: [] show_trace_log_lvl+0x58/0x171 [] show_trace+0xd/0x10 [] dump_stack+0x19/0x1b [] __lock_acquire+0x778/0x99c [] lock_acquire+0x4b/0x6d [] lock_sock+0xac/0xbc [] bt_accept_dequeue+0x26/0xc6 [bluetooth] [] l2cap_sock_accept+0xe2/0x11e [l2cap] [] sys_accept+0xd8/0x179 [] sys_socketcall+0xa7/0x186 [] syscall_call+0x7/0xb DWARF2 unwinder stuck at syscall_call+0x7/0xb Leftover inexact backtrace: [] show_trace+0xd/0x10 [] dump_stack+0x19/0x1b [] __lock_acquire+0x778/0x99c [] lock_acquire+0x4b/0x6d [] lock_sock+0xac/0xbc [] bt_accept_dequeue+0x26/0xc6 [bluetooth] [] l2cap_sock_accept+0xe2/0x11e [l2cap] [] sys_accept+0xd8/0x179 [] sys_socketcall+0xa7/0x186 [] syscall_call+0x7/0xb