Re: irda rmmod lockdep trace.

[Samuel Ortiz]

Hi Dave,

On Thu, Mar 08, 2007 at 05:54:36PM -0500, Dave Jones wrote:
> modprobe irda ; rmmod irda in 2.6.21rc3 gets me the spew below..
Well it seems that we call __irias_delete_object() from hashbin_delete(). Then
__irias_delete_object() calls itself hashbin_delete() again. We're trying to
get the lock recursively.
I'll try to fix that soon, thanks for the report.

Cheers,
Samuel.


> 	Dave
> 
> NET: Registered protocol family 23
> NET: Unregistered protocol family 23
> 
> =============================================
> [ INFO: possible recursive locking detected ]
> 2.6.20-1.2966.fc7 #1
> ---------------------------------------------
> rmmod/16712 is trying to acquire lock:
>  (&hashbin->hb_spinlock){....}, at: [<ffffffff884bf476>] hashbin_delete+0x29/0x94 [irda]
> 
> but task is already holding lock:
>  (&hashbin->hb_spinlock){....}, at: [<ffffffff884bf476>] hashbin_delete+0x29/0x94 [irda]
> 
> other info that might help us debug this:
> 1 lock held by rmmod/16712:
>  #0:  (&hashbin->hb_spinlock){....}, at: [<ffffffff884bf476>] hashbin_delete+0x29/0x94 [irda]
> 
> stack backtrace:
> 
> Call Trace:
>  [<ffffffff802a303b>] __lock_acquire+0x151/0xbc4
>  [<ffffffff884c1517>] :irda:__irias_delete_attrib+0x0/0x31
>  [<ffffffff802a3ea4>] lock_acquire+0x4c/0x65
>  [<ffffffff884bf476>] :irda:hashbin_delete+0x29/0x94
>  [<ffffffff80264011>] _spin_lock_irqsave+0x2c/0x3c
>  [<ffffffff884bf476>] :irda:hashbin_delete+0x29/0x94
>  [<ffffffff884c1918>] :irda:__irias_delete_object+0x0/0x39
>  [<ffffffff884c193d>] :irda:__irias_delete_object+0x25/0x39
>  [<ffffffff884bf48d>] :irda:hashbin_delete+0x40/0x94
>  [<ffffffff884c5e3a>] :irda:iriap_cleanup+0x36/0x38
>  [<ffffffff884c5fd6>] :irda:irda_cleanup+0x29/0x3a
>  [<ffffffff802aa1e1>] sys_delete_module+0x199/0x1ca
>  [<ffffffff8026ce36>] syscall_trace_enter+0x9a/0x9f
>  [<ffffffff8025c2b5>] tracesys+0xdc/0xe1
> 
> 
> -- 
> http://www.codemonkey.org.uk

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/