> The warning that triggered (lockdep.c:700) means that one class (key) > was used with more than one name.
Right. > Looking at cleanup_workqueue_thread(), the lock_acquire() there works on > wq->lockdep_map, and that is only initialized at one spot: > __create_workqueue_key(), thus it stands to reason that that was > mis-used. Oh ok, yes, makes sense. Maybe something is generating a workqueue with a name that's passed in but the key is statically from that place. I'll try to find it. johannes
signature.asc
Description: This is a digitally signed message part