From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1343] net/i40e does not drop packet with too many segments
Date: Fri, 05 Jan 2024 13:44:32 +0000 [thread overview]
Message-ID: <bug-1343-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1343
Bug ID: 1343
Summary: net/i40e does not drop packet with too many segments
Product: DPDK
Version: 23.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: andrew.rybchenko@oktetlabs.ru
Target Milestone: ---
net/i40e does not drop packet with too many segments
The test case is a bit artificial, but still makes sense. If application sent
packet with too many segments which do not fit in Tx ring (or free space in Tx
ring) the packet is reported as sent anyway.
The packet is not counted as sent in stats or output errors.
The following errors appear in logs:
i40e_dev_alarm_handler(): ICR0: malicious programming detected
i40e_handle_mdd_event(): Malicious Driver Detection event 0x02 on TX queue 1 PF
number 0x00 VF number 0x00
device 0000:01:00.0
Should be repeatable with testpmd which allows to sent packet with many
segments. E.g. setup Tx queue with 64 descriptors and try to send packet with
65 segments.
IMHO right behaviour in this case is to report the packet as transmitted in Tx
burst return value, but drop and count it in oerrors. (Otherwise Tx could
stuck).
Test logs (run at UHN IOL):
https://ts-factory.io/bublik/v2/log/362398?focusId=368819&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_60
Mentioned error appear in logs with delay (in the next test):
https://ts-factory.io/bublik/v2/log/362398?focusId=368820&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_32
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3964 bytes --]
reply other threads:[~2024-01-05 13:44 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-1343-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).