From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1068] [20.11] creating a rule with a shared action after port restart causes a segfault
Date: Thu, 18 Aug 2022 15:03:43 +0000 [thread overview]
Message-ID: <bug-1068-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1068
Bug ID: 1068
Summary: [20.11] creating a rule with a shared action after
port restart causes a segfault
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
To reproduce:
$ sudo ./build/app/dpdk-testpmd -n 4 -a 0000:08:00.0 -- -i --rxq=4 --txq=4
--hairpinq=8 --hairpin-mode=0x12
[..]
testpmd> flow shared_action 0 destroy action_id 1
testpmd> flow shared_action 0 create action_id 1 ingress action rss queues 9 8
end level 2 types ipv6 l3-dst-only end func default key_len 40 / end
Shared action #1 created
testpmd> port stop 0
testpmd> port start 0
testpmd> flow shared_action 0 destroy action_id 1
port_flow_complain(): Caught PMD error type 16 (specific action): invalid
shared action: Invalid argument
testpmd> flow validate 0 priority 0 ingress group 0 pattern eth / end actions
set_mac_dst mac_addr 00:16:3e:3f:0f:4f / shared 1 / end
Segmentation fault
OS: Ubuntu 20.04
OFED: MLNX_OFED_LINUX-5.7-1.0.2.0
Device: ConnectX-5
Firmware: 16.34.1002
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-08-18 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 15:03 bugzilla [this message]
2022-08-18 15:45 ` [Bug 1068] [20.11] creating a rule with a shared action after port restart causes a segfault bugzilla
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-1068-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.