netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue
@ 2006-09-17 11:36 Pekka Pietikainen
  2006-09-17 12:18 ` Marcel Holtmann
  0 siblings, 1 reply; 3+ messages in thread
From: Pekka Pietikainen @ 2006-09-17 11:36 UTC (permalink / raw)
  To: marcel; +Cc: netdev

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue
  2006-09-17 11:36 [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue Pekka Pietikainen
@ 2006-09-17 12:18 ` Marcel Holtmann
  2006-09-17 18:32   ` Pekka Pietikainen
  0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2006-09-17 12:18 UTC (permalink / raw)
  To: Pekka Pietikainen; +Cc: netdev

Hi Pekka,

> 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

what where you doing when this happened?

Regards

Marcel



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue
  2006-09-17 12:18 ` Marcel Holtmann
@ 2006-09-17 18:32   ` Pekka Pietikainen
  0 siblings, 0 replies; 3+ messages in thread
From: Pekka Pietikainen @ 2006-09-17 18:32 UTC (permalink / raw)
  To: Marcel Holtmann; +Cc: netdev

On Sun, Sep 17, 2006 at 02:18:26PM +0200, Marcel Holtmann wrote:
> Hi Pekka,
> 
> > 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]
> 
> what where you doing when this happened?
Hiya

Hmn. Plugged my USB BT dongle in, started gnome-obex-server and sent a few
pictures from my cellphone to the box, nothing fancy.. Bluetooth daemons
running obviously at this time...



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-09-17 18:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-17 11:36 [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue Pekka Pietikainen
2006-09-17 12:18 ` Marcel Holtmann
2006-09-17 18:32   ` Pekka Pietikainen

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).