From: David Ahern <dsahern@kernel.org>
To: hanhuihui <hanhuihui5@huawei.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"pablo@netfilter.org" <pablo@netfilter.org>
Cc: "Yanan (Euler)" <yanan@huawei.com>,
Caowangbao <caowangbao@huawei.com>,
"Fengtao (fengtao, Euler)" <fengtao40@huawei.com>,
liaichun <liaichun@huawei.com>
Subject: Re: The call trace occurs during the VRF fault injection test
Date: Mon, 11 Sep 2023 09:47:15 -0600 [thread overview]
Message-ID: <01d3caaa-42b7-58a1-e0e4-7578ecd10d0e@kernel.org> (raw)
In-Reply-To: <1c353f53578e48faa9b254394b42b391@huawei.com>
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.
next prev parent reply other threads:[~2023-09-11 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 10:05 The call trace occurs during the VRF fault injection test hanhuihui
2023-09-11 15:47 ` David Ahern [this message]
2023-09-18 12:39 ` Fengtao (fengtao, Euler)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01d3caaa-42b7-58a1-e0e4-7578ecd10d0e@kernel.org \
--to=dsahern@kernel.org \
--cc=caowangbao@huawei.com \
--cc=davem@davemloft.net \
--cc=fengtao40@huawei.com \
--cc=hanhuihui5@huawei.com \
--cc=liaichun@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=yanan@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).