Re: [BISECTED] Linux 3.2: Networking out of LAN does not work
From: Eric Dumazet <hidden>
Date: 2012-01-25 09:45:34
Le mercredi 25 janvier 2012 à 10:40 +0100, Eric Dumazet a écrit :
Le mercredi 25 janvier 2012 à 10:35 +0100, Rune Magnussen a écrit :quoted
Hi Networking to and from the outside of my LAN does not work with Linux 3.2.x. Linux 3.1.x works. Using ssh from a PC on the LAN also works. The machine has a VIA C7 CPU and the NIC uses the 8139too-driver. Another machine with a r8169-NIC and an Atom-CPU (32bit) did not show any problems. It was used very ligtly though. Bisection led to this: --- f04565ddf52e401880f8ba51de0dff8ba51c99fd is the first bad commit commit f04565ddf52e401880f8ba51de0dff8ba51c99fd Author: Mihai Maruseac [off-list ref] Date: Thu Oct 20 20:45:10 2011 +0000 dev: use name hash for dev_seq_ops Instead of using the dev->next chain and trying to resync at each call to dev_seq_start, use the name hash, keeping the bucket and the offset in seq->private field. Tests revealed the following results for ifconfig > /dev/null * 1000 interfaces: * 0.114s without patch * 0.089s with patch * 3000 interfaces: * 0.489s without patch * 0.110s with patch * 5000 interfaces: * 1.363s without patch * 0.250s with patch * 128000 interfaces (other setup): * ~100s without patch * ~30s with patch Signed-off-by: Mihai Maruseac [off-list ref] Signed-off-by: Eric Dumazet [off-list ref] Signed-off-by: David S. Miller [off-list ref] :040000 040000 2e86e1c9ecaf719d312a8b5863ec9e89d92bc4b3 8b0d09ca105502dd5389bb6281ef059c8bb38667 M net --- Simply reverting the commit on top of Linux 3.2.1 resultet in a build error. Used kernel configuration: http://knus.info/kernel/config-3.1.txt Greetings RuneIt might be a userland error, because order of devices might be different in : ip link cat /proc/net/dev
Or it also be a bug introduced by this commit and fixed in 5cac98dd06bc43a (net: Fix corruption in /proc/*/net/dev_mcast)