| 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: <20110321063712.GB2836@psychotron.redhat.com> Date: Mon, 21 Mar 2011 07:37:13 +0100 From: Jiri Pirko <jpirko@...hat.com> To: Nicolas de Pesloüan <nicolas.2p.debian@...il.com> Cc: Jay Vosburgh <fubar@...ibm.com>, Andy Gospodarek <andy@...yhouse.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: oops / kernel panic in bonding. Sun, Mar 20, 2011 at 10:19:21PM CET, nicolas.2p.debian@...il.com wrote: >Le 20/03/2011 21:17, Nicolas de Pesloüan a écrit : >>Hi Jiri, >> >>I suspect we have a race condition somewhere in the new >>bond_handle_frame function: >> >>The following commands produce one of the following errors: >> >>modprobe bonding max_bonds=0 >>echo +bond0>/sys/class/net/bonding_masters >>echo +bond1>/sys/class/net/bonding_masters >>echo +eth1>/sys/class/net/bond1/bonding/slaves >> >>This is mostly reproducible, under VirtualBox. >> >>All tests done with 08351fc6a75731226e1112fc7254542bd3a2912e at the top >>commit (current net-next-2.6). > >I suspect netdev_rx_handler_register is called too early in bond_enslave. > >I think it should be the last thing we do in bond_enslave, if we >don't want to face the risk to have bond_handle_frame being called >before everything is properly setup. > > Nicolas. Hmm, Offset 0x280 is big, I suggest dev->master is not set. Will look at this. -- 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