| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20080328.173414.22278840.davem@davemloft.net> Date: Fri, 28 Mar 2008 17:34:14 -0700 (PDT) From: David Miller <davem@...emloft.net> To: davej@...emonkey.org.uk Cc: netdev@...r.kernel.org Subject: Re: 2.6.25rc7 lockdep trace From: Dave Jones <davej@...emonkey.org.uk> Date: Thu, 27 Mar 2008 20:00:13 -0400 > stack backtrace: > Pid: 2308, comm: NetworkManager Not tainted 2.6.25-0.161.rc7.fc9.i686 #1 > [print_circular_bug_tail+91/102] print_circular_bug_tail+0x5b/0x66 > [print_circular_bug_entry+57/67] ? print_circular_bug_entry+0x39/0x43 > [__lock_acquire+2488/3089] __lock_acquire+0x9b8/0xc11 > [_spin_unlock_irq+34/47] ? _spin_unlock_irq+0x22/0x2f > [lock_acquire+106/144] lock_acquire+0x6a/0x90 > [flush_workqueue+0/133] ? flush_workqueue+0x0/0x85 > [flush_workqueue+68/133] flush_workqueue+0x44/0x85 > [flush_workqueue+0/133] ? flush_workqueue+0x0/0x85 > [flush_scheduled_work+13/15] flush_scheduled_work+0xd/0xf > [<d096d80a>] tulip_down+0x20/0x1a3 [tulip] > [trace_hardirqs_on+233/266] ? trace_hardirqs_on+0xe9/0x10a > [dev_deactivate+177/222] ? dev_deactivate+0xb1/0xde Yes, see for example: http://www.mail-archive.com/netdev@vger.kernel.org/msg31718.html You can't flush a workqueue in the device close handler exactly because of this locking conflict. Nobody has come up with a suitable way to fix this yet. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists