> [ INFO: possible circular locking dependency detected ]
> 2.6.25-rc8-wl #23
> -------------------------------------------------------
> rmmod/5589 is trying to acquire lock:
> ((name)){--..}, at: [<c012deec>] flush_workqueue+0x0/0x80
>
> but task is already holding lock:
> (rtnl_mutex){--..}, at: [<c02507ee>] rtnl_lock+0xf/0x11
>
> which lock already depends on the new lock.
Huh, yes, but why didn't this show up before? The bug has been there
*forever* and my workqueue lockdep debugging has been in the kernel for
a long time as well. Odd.
I think the solution is to use cancel_work_sync() but I'll have to look
into it.
johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
