Il 23.05.2015 16:40 ebied...@xmission.com ha scritto:
The reproducer was apparently: ip netns add ns0 ip netns add ns1 ip link add test0 type veth peer name test1 ip link set test0 netns ns0 ip link set test1 netns ns1 ip netns exec ns0 sysctl net.ipv4.ip_forward=1 ip netns exec ns1 sysctl net.ipv4.ip_forward=1 ip netns exec ns0 sysctl net.ipv4.conf.all.accept_local=1 ip netns exec ns1 sysctl net.ipv4.conf.all.accept_local=1 ip netns exec ns0 sysctl net.ipv4.conf.test0.accept_local=1 ip netns exec ns1 sysctl net.ipv4.conf.test1.accept_local=1 ip netns exec ns0 sysctl net.ipv4.conf.all.send_redirects=0 ip netns exec ns1 sysctl net.ipv4.conf.all.send_redirects=0 ip netns exec ns0 sysctl net.ipv4.conf.test0.send_redirects=0 ip netns exec ns1 sysctl net.ipv4.conf.test1.send_redirects=0 ip netns exec ns0 ip addr add 10.10.10.1/24 dev test0 ip netns exec ns1 ip addr add 10.10.10.2/24 dev test1 ip netns exec ns0 ip link set up dev test0 ip netns exec ns1 ip link set up dev test1 ip netns exec ns0 ip route add 10.20.30.40 via 10.10.10.2 dev test0 ip netns exec ns1 ip route add 10.20.30.40 via 10.10.10.1 dev test1 ip netns exec ns0 iptables -t mangle -A PREROUTING -i test0 -j TTL --ttl-inc 1 ip netns exec ns1 iptables -t mangle -A PREROUTING -i test1 -j TTL --ttl-inc 1 ip netns exec ns0 ping -s 1400 -f -w 5 10.20.30.40 ip netns delete ns0 ip netns delete ns1
Yes, and the commands were ultimately wrapped in a "while true; do ... done" loop, since the crash would not happen every time, but it eventually will, without the patch. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
