From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Vladimir Medvedkin" <vladimir.medvedkin@intel.com>
Cc: <dev@dpdk.org>
Subject: Intel IAVF base driver structure definition is wrong
Date: Wed, 29 Apr 2026 13:48:06 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F6582E@smartserver.smartshare.dk> (raw)
Hi Vladimir,
This build failure seems to be caused by a bug in the IAVF base driver:
https://github.com/ovsrobot/dpdk/actions/runs/25104438552/job/73561907869#step:19:803
struct virtchnl_rss_key {
u16 vsi_id;
u16 key_len;
u8 key[1]; /* RSS hash key, packed bytes */
};
The "key[1]" should be "key[]".
And when copying to it, remember to change "sizeof(struct virtchnl_rss_key) - 1" to "sizeof(struct virtchnl_rss_key)".
Other Intel drivers may have the same bug.
Venlig hilsen / Kind regards,
-Morten Brørup
-----Original Message-----
From: 0-day Robot [mailto:robot@bytheb.org]
Sent: Wednesday, 29 April 2026 13.25
To: test-report@dpdk.org
Cc: Morten Brørup; robot@bytheb.org
Subject: |FAILURE| pw163367 [PATCH v9] eal/x86: optimize memcpy of small sizes
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
https://patchwork.dpdk.org/patch/163367/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/25104438552
reply other threads:[~2026-04-29 11:48 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=98CBD80474FA8B44BF855DF32C47DC35F6582E@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=vladimir.medvedkin@intel.com \
/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