From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B04DC45744; Mon, 5 Aug 2024 21:44:47 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AE6C3402A1; Mon, 5 Aug 2024 21:44:46 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id E39FF40295 for ; Mon, 5 Aug 2024 21:44:44 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id C86C045745; Mon, 5 Aug 2024 21:44:44 +0200 (CEST) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: testpmd X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jspewock@iol.unh.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17228870840.C12Ea.1797029 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17228870840.C12Ea.1797029 Date: Mon, 5 Aug 2024 21:44:44 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1514 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 informat= ion 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 pac= ket 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 structu= re to the testpmd shell that is forwarding with verbose mode set to 1: `pakt =3D Ether() / IP(chksum=3D0x0)` --=20 You are receiving this mail because: You are the assignee for the bug.= --17228870840.C12Ea.1797029 Date: Mon, 5 Aug 2024 21:44:44 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
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 mo=
de 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 inf=
ormation
about the RX IP checksum" and `RTE_MBUF_F_RX_IP_CKSUM_BAD` should be s=
hown 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 pac=
ket
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 structu=
re
to the testpmd shell that is forwarding with verbose mode set to 1:

`pakt =3D Ether() / IP(chksum=3D0x0)`

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17228870840.C12Ea.1797029--