From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 615] testpmd gets stuck when deleting an FDIR flow
Date: Thu, 14 Jan 2021 13:33:43 +0000 [thread overview]
Message-ID: <bug-615-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=615
Bug ID: 615
Summary: testpmd gets stuck when deleting an FDIR flow
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
When deleting a specific FDIR rule (see the last rule below), testpmd will get
stuck.
To reproduce:
- Run testpmd:
testpmd -n 4 -w 0000:00:05.0 -w 0000:00:06.0 -- -i --rxq=2 --txq=2
--pkt-filter-mode perfect
- Run the following commands in testpmd. The last one will cause testpmd to get
stuck, but I wasn't able to get a trace:
"""
port stop all
flow_director_mask 0 mode IP vlan 0 src_mask 0.0.0.0
ffff:ffff:ffff:ffff:ffff:0:0:0 0xfff0 dst_mask 0.0.0.0
ffff:ffff:ffff:ffff:ffff:0:0:0 0xff00
flow_director_mask 1 mode IP vlan 0 src_mask 0.0.0.0
ffff:ffff:ffff:ffff:ffff:0:0:0 0xfff0 dst_mask 0.0.0.0
ffff:ffff:ffff:ffff:ffff:0:0:0 0xff00
port start all
start
flow_director_filter 0 mode IP add flow ipv6-tcp src ::a209 27758 dst ::1805
12298 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 1 fd_id 1
flow_director_filter 1 mode IP add flow ipv6-tcp src ::a209 27758 dst ::1805
12298 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 1 fd_id 1
flow_director_filter 0 mode IP add flow ipv6-udp src ::ff08 40983 dst ::268e
19741 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 1 mode IP add flow ipv6-udp src ::ff08 40983 dst ::268e
19741 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 0 mode IP add flow ipv4-other src 0.143.50.94 286 dst
107.219.10.119 55222 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) drop pf queue 1
fd_id 1
flow_director_filter 1 mode IP add flow ipv4-other src 0.143.50.94 286 dst
107.219.10.119 55222 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) drop pf queue 1
fd_id 1
flow_director_filter 0 mode IP add flow ipv6-udp src ::cff5 26958 dst ::f978
6084 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 1 fd_id 1
flow_director_filter 1 mode IP add flow ipv6-udp src ::cff5 26958 dst ::f978
6084 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 1 fd_id 1
flow_director_filter 0 mode IP add flow ipv6-udp src ::3962 29380 dst ::4fd0
40864 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 1 mode IP add flow ipv6-udp src ::3962 29380 dst ::4fd0
40864 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 0 mode IP add flow ipv4-other src 252.195.129.146 26073
dst 15.5.47.129 7690 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) drop pf queue 0
fd_id 1
flow_director_filter 1 mode IP add flow ipv4-other src 252.195.129.146 26073
dst 15.5.47.129 7690 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) drop pf queue 0
fd_id 1
flow_director_filter 0 mode IP add flow ipv6-udp src ::971a 40172 dst ::44a7
35151 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 1 mode IP add flow ipv6-udp src ::971a 40172 dst ::44a7
35151 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 0 mode IP add flow ipv6-udp src ::9e3 5063 dst ::72e8
58832 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 1 mode IP add flow ipv6-udp src ::9e3 5063 dst ::72e8
58832 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 0 mode IP add flow ipv6-udp src ::4b1d 38458 dst ::6689
52498 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 1 mode IP add flow ipv6-udp src ::4b1d 38458 dst ::6689
52498 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 0 mode IP add flow ipv6-udp src ::ebb9 32643 dst ::514
2600 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 1 mode IP add flow ipv6-udp src ::ebb9 32643 dst ::514
2600 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 0 mode IP del flow ipv6-tcp src ::a209 27758 dst ::1805
12298 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 1 fd_id 1
flow_director_filter 1 mode IP del flow ipv6-tcp src ::a209 27758 dst ::1805
12298 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 1 fd_id 1
flow_director_filter 0 mode IP del flow ipv6-udp src ::ff08 40983 dst ::268e
19741 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 1 mode IP del flow ipv6-udp src ::ff08 40983 dst ::268e
19741 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 0 mode IP del flow ipv4-other src 0.143.50.94 286 dst
107.219.10.119 55222 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) drop pf queue 1
fd_id 1
flow_director_filter 1 mode IP del flow ipv4-other src 0.143.50.94 286 dst
107.219.10.119 55222 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) drop pf queue 1
fd_id 1
flow_director_filter 0 mode IP del flow ipv6-udp src ::cff5 26958 dst ::f978
6084 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 1 fd_id 1
flow_director_filter 1 mode IP del flow ipv6-udp src ::cff5 26958 dst ::f978
6084 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 1 fd_id 1
flow_director_filter 0 mode IP del flow ipv6-udp src ::3962 29380 dst ::4fd0
40864 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 1 mode IP del flow ipv6-udp src ::3962 29380 dst ::4fd0
40864 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) fwd pf queue 0 fd_id 1
flow_director_filter 0 mode IP del flow ipv4-other src 252.195.129.146 26073
dst 15.5.47.129 7690 tos 0 ttl 0 vlan 0x0 flexbytes (0x0,0x0) drop pf queue 0
fd_id 1
"""
This also reproduces in newer releases that still have legacy FDIR filter type
support.
NIC: ConnectX-5
OFED: MLNX_OFED_LINUX-5.2-1.0.4.0
Firmware version: 16.29.1016
OS: RHEL 7.4
Kernel: 3.10.0-693.el7.x86_64
gcc: 4.8.5
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-01-14 13:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-615-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).