| 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
| ||
|
Date: Thu, 06 Mar 2008 15:56:40 -0500 From: jamal <hadi@...erus.ca> To: Jarek Poplawski <jarkao2@...il.com> Cc: Denys Fedoryshchenko <denys@...p.net.lb>, netdev@...r.kernel.org Subject: Re: circular locking, mirred, 2.6.24.2 On Thu, 2008-06-03 at 21:25 +0100, Jarek Poplawski wrote: > It's really strange: I can't reproduce this, I couldnt either - are you using 2.6.25-rc4? > and if it were so easy we > would get really a lot of similar reports. It looks like you have > something special. This lockdep report with this kind of problem > usually looks different too. The good side is it's easy to reproduce. > So, could you try the patch below? (It's only supposed to fix the lockdep > warning, not lockups). This is more out of ignorance: Why is ifb needing the extra teaching for lockdep? It is a netdevice - shouldnt the two global lockdeps you described earlier not be sufficient? cheers, jamal -- 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