From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1111] i40e: buffer size fields may overflow in Rx descriptors
Date: Wed, 19 Oct 2022 12:57:23 +0000 [thread overview]
Message-ID: <bug-1111-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1111
Bug ID: 1111
Summary: i40e: buffer size fields may overflow in Rx
descriptors
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: ---
Created attachment 226
--> https://bugs.dpdk.org/attachment.cgi?id=226&action=edit
probable-fix
It appears that opensource ethdev tests [1] have detected a bug in
i40e PMD: by the looks of it, Rx descriptor fill-out is not robust
against overflow in data buffer size field, which happens when the
user provides a mempool with excessively large objects on Rx setup.
A test log example can be found at [2]. In it, a mempool with mbuf
data size of 32900 B is used. The test sends one packet to the NIC,
but the PMD sees 5 packets which have no payload. Manual debugging
indicates that, in the driver, round-up gives the value of 32768 B,
which then gives the value of 256 to use in 7-bit "dbuff" field of
an Rx descriptor ([3]). The value overflows, hence the test result.
A probable fix is attached to the ticket.
[1] http://mails.dpdk.org/archives/dev/2022-October/251663.html
[2] https://ts-factory.io/bublik/v2/log/123183?focusId=123879&mode=treeAndlog
[3]
https://github.com/DPDK/dpdk/blob/main/drivers/net/i40e/base/i40e_lan_hmc.c#L709
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-10-19 12:57 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-1111-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).