[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01d3caaa-42b7-58a1-e0e4-7578ecd10d0e@kernel.org>
Date: Mon, 11 Sep 2023 09:47:15 -0600
From: David Ahern <dsahern@...nel.org>
To: hanhuihui <hanhuihui5@...wei.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"pablo@...filter.org" <pablo@...filter.org>
Cc: "Yanan (Euler)" <yanan@...wei.com>, Caowangbao <caowangbao@...wei.com>,
"Fengtao (fengtao, Euler)" <fengtao40@...wei.com>,
liaichun <liaichun@...wei.com>
Subject: Re: The call trace occurs during the VRF fault injection test
On 9/8/23 4:05 AM, hanhuihui wrote:
> Hello, I found a problem in the VRF fault injection test scenario. When the size of the sent data packet exceeds the MTU, the call trace is triggered. The test script and detailed error information are as follows:
> "ip link add name vrf-blue type vrf table 10
> ip link set dev vrf-blue up
> ip route add table 10 unreachable default
> ip link set dev enp4s0 master vrf-blue
> ip address add 192.168.255.250/16 dev enp4s0
> tc qdisc add dev enp4s0 root netem delay 1000ms 500ms
> tc qdisc add dev vrf-blue root netem delay 1000ms 500ms
> ip vrf exec vrf-blue ping "192.168.162.184" -s 6000 -I "enp4s0" -c 3
> tc qdisc del dev "enp4s0" root
> tc qdisc del dev vrf-blue root
> ip address del 192.168.255.250/16 dev enp4s0
> ip link set dev enp4s0 nomaster"
>
Thanks for the reproducer. I will take a look when I get some time.
Powered by blists - more mailing lists