From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/testpmd Bug 1514] mlx5 NIC reports checksum unknown when an invalid checksum is present
Date: Mon, 05 Aug 2024 19:44:44 +0000 [thread overview]
Message-ID: <bug-1514-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1514
Bug ID: 1514
Summary: mlx5 NIC reports checksum unknown when an invalid
checksum is present
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: jspewock@iol.unh.edu
Target Milestone: ---
When running testpmd in verbose mode on a NIC that uses the mlx5_core PMD, if
you send a packet with an invalid IP checksum it will show the ol_flag
`RTE_MBUF_F_RX_IP_CKSUM_UNKNOWN` when it should be
`RTE_MBUF_F_RX_IP_CKSUM_BAD`. According to lib/mbuf/rte_mbuf_core.h
`RTE_MBUF_F_RX_IP_CKSUM_UNKNOWN` should be shown when there is "no information
about the RX IP checksum" and `RTE_MBUF_F_RX_IP_CKSUM_BAD` should be shown when
"the IP checksum in the packet is wrong". This leads to an issue currently
where, from verbose output in testpmd, you cannot distinguish between a packet
having a bad checksum and one not being present at all. It should be noted that
this is also the case for L4 and OUTER_L4 checksums as well.
You can reproduce this by sending a scapy packet with the following structure
to the testpmd shell that is forwarding with verbose mode set to 1:
`pakt = Ether() / IP(chksum=0x0)`
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3407 bytes --]
reply other threads:[~2024-08-05 19: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-1514-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).