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:45:35 +0000 [thread overview]
Message-ID: <bug-1068-3-HY4ssyNmMi@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1068-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=1068
Dmitry Kozlyuk (dkozlyuk@nvidia.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Dmitry Kozlyuk (dkozlyuk@nvidia.com) ---
Before 21.11 it was unspecified whether indirect actions are kept across port
restart. Since 21.11 there is RTE_ETH_DEV_CAPA_SHARED_OBJECT_KEEP to indicate
the behavior. This is a new feature that cannot be backported. The only way to
ensure predictable behavior with any PMD before 21.11 is to destroy indirect
actions before port stop.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-08-18 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 15:03 bugzilla
2022-08-18 15:45 ` bugzilla [this message]
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-HY4ssyNmMi@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).