[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fcd2798f213a4eae982db78cf3019197@akamai.com>
Date: Sat, 2 Nov 2024 09:11:31 +0000
From: "Mortensen, Christian" <cworm@...mai.com>
To: "davem@...emloft.net" <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Stackoverflow when using seg6 routes
> The following script consistently reproduces the problem for me. It is probably not minimal:
I was able to trim down the script somewhat:
# Setup host1 with strange routing.
ip netns add host1
ip netns exec host1 ip link set dev lo up
ip netns exec host1 sysctl net.ipv4.ip_forward=1
ip netns exec host1 sysctl net.vrf.strict_mode=1
ip netns exec host1 ip link add vrf9 type vrf table 1009
ip netns exec host1 ip link set vrf9 up
ip netns exec host1 ip route add fc00:0:0:1:7:: encap seg6local action End.DT4 vrftable 1009 dev vrf9
ip netns exec host1 ip route add 192.168.2.1 encap seg6 mode encap segs fc00:0:0:1:7:: via inet6 fe80::2 dev lo vrf vrf9
# Send a ping to vrf9 to crash the kernel:
ip netns add host1_1
ip netns exec host1 ip link add vm1 type veth peer eth0 netns host1_1
ip netns exec host1 ip link set vm1 master vrf9
ip netns exec host1 ip link set vm1 up
ip netns exec host1 sysctl net.ipv4.conf.vm1.proxy_arp=1
ip netns exec host1 ip route add 192.168.1.1/32 dev vm1 vrf vrf9
ip netns exec host1_1 ip link set eth0 up
ip netns exec host1_1 ip addr add dev eth0 192.168.1.1/16
ip netns exec host1_1 ping 192.168.2.1
Powered by blists - more mailing lists