From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 581] iavf_fdir: wrongly use rte_flow_item_* for copy to build protocol hdr
Date: Sun, 22 Nov 2020 13:06:02 +0000 [thread overview]
Message-ID: <bug-581-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=581
Bug ID: 581
Summary: iavf_fdir: wrongly use rte_flow_item_* for copy to
build protocol hdr
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: jackmin@nvidia.com
Target Milestone: ---
iavf_fdir_parse_pattern uses the rte_flow_item_* struct as original data for
copy to build hdr buffer. It assumes rte_flow_item_* struct represent the real
protocol header but this assumption is not true[1][2].
[1]:
commit 09315fc83861 ("ethdev: add VLAN attributes to ethernet and VLAN items")
[2]:
commit ad976bd40d28 ("ethdev: add extensions attributes to IPv6 item")
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-11-22 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 13:06 bugzilla [this message]
2020-12-30 7:18 ` 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-581-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).