netdev - Re: [PROBLEM] Bonding driver in linux-2.6.21-rc6-mm1

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 29 Apr 2007 00:04:31 +0200
From:	Vincent ETIENNE <ve@...ienne.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	netdev@...r.kernel.org
Subject: Re: [PROBLEM] Bonding driver in linux-2.6.21-rc6-mm1

Le Saturday 28 April 2007 23:31:02 Andrew Morton, vous avez écrit :
>
> > Is there anything i can do to get you more precise information ?
>
> I guess if you could provide us with your .config and a step-by-step recipe
> which developers should use to reproduce the problem then we should be able
> to fix this pretty easily when someone finds the time to do so.

For the config, i have uploaded it to 
http://mail1.vetienne.net/linux/config-2.6.21-rc7-mm2. 

For reproducing the problem, it 's simple (for me at least) :

	-  setup a bonding interface ( IP 192.168.1.5/255.255.255.0 so nothing 
fancy ) bond (mode 6 : alb ) on two NIC card (in my case  E1000 and TG3 ). 
Don't know if it's important or not but the two cards are connected to the 
same cheap 100Mb switch ( So no gigabit )

	- Reboot  : when the bond interface went up ( after the two physical slaves ) 
the bug is triggered ( for the moment always, but i have only rebooted 2 or 3 
times with 2.6.21-rc7-mm2  ).

	- You could also play with networks cable and put down/up one interface or 
another  during normal work : it would often triggered the same trace ( not 
always although ). You don't need to have load on the network. The interface 
that went down or up doesn't seem to be important as far as i can see.

	- No lockup of the kernel, network still work fine after the problem







-
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