From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1113] i40e: device configure ignores RSS key in rx_adv_conf
Date: Tue, 25 Oct 2022 11:52:18 +0000 [thread overview]
Message-ID: <bug-1113-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1113
Bug ID: 1113
Summary: i40e: device configure ignores RSS key in rx_adv_conf
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: ivan.malov@oktetlabs.ru
Target Milestone: ---
Running the opensource ethdev test suite [1] on a i40e rig suggests that the
PMD
might have a bug in its device configure method. In particular, RSS key size
and
data passed by the caller as part of "rx_adv_conf" seem to be completely
ignored.
If the caller makes a mistake in the key size, they won't be informed about
that.
This way, the caller may be tricked into thinking that "rx_adv_conf" is
accepted.
However, if they try to predict a hash using this key, the result won't be
valid.
A log example can be found at [2].
[1] http://mails.dpdk.org/archives/dev/2022-October/251663.html
[2] https://ts-factory.io/bublik/v2/log/70553?focusId=70999&mode=treeAndlog
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-10-25 11:52 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-1113-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).