| 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: <1315958348.2565.22.camel@edumazet-laptop> Date: Wed, 14 Sep 2011 01:59:08 +0200 From: Eric Dumazet <eric.dumazet@...il.com> To: Murali raja Muniraju <murali.rajam@...il.com> Cc: netdev@...r.kernel.org Subject: Re: Query on a lockdep issue in neigh_lookup Le mardi 13 septembre 2011 à 16:11 -0700, Murali raja Muniraju a écrit : > Hi, > I see a potential deadlock situation on the kernel 2.6.34. Has this > been fixed in the later version of the kernel. > > I see that one after holding the neigh_lookup, one can acquire the > lock for rt_hash_locks > > But there is a situation while freed skb's in dst_release while > holding the rt_hash_locks, neigh_lookup can be called which tries to > acquire its lock. > > This seems to be a deadlock candidate. > > Thanks, > Murali > > Below if the scenario found by lockdep on a debug kernel during the > kernel bootup. > All this code changed in 2.6.37 with commit d6bf781712a1d25cc8987036b3a48535b331eb91 (net neigh: RCU conversion of neigh hash table) -- 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