From: Raslan Darawsheh <rasland@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "haijie1@huawei.com" <haijie1@huawei.com>
Subject: Re: [PATCH] app/testpmd: fix VLAN header parsing
Date: Mon, 24 Mar 2025 07:38:40 +0000 [thread overview]
Message-ID: <CH3PR12MB846087E8B2CE0A1A443C9903CFA42@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <5993081.QJadu78ljV@thomas>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
>> Updated the `get_ethertype_by_ptype` function to correctly parse VLAN
>> headers.
>You should describe what is broken and how.
I’ll handle in v2
>> Fixes: 76730c7b9b5a ("app/testpmd: use packet type parsing API")
>> Cc: haijie1@huawei.com
>Do you think it is critical for the release?
Yes, as it’s causing an infinite loop if you send a QinQ packet with csum fwd, and it will cause tested to get stuck forever.
[-- Attachment #2: Type: text/html, Size: 2956 bytes --]
next prev parent reply other threads:[~2025-03-24 7:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 12:28 Raslan Darawsheh
2025-03-23 13:14 ` Morten Brørup
2025-03-24 7:34 ` Raslan Darawsheh
2025-03-24 7:43 ` Morten Brørup
2025-03-24 7:44 ` Morten Brørup
2025-03-24 8:32 ` Raslan Darawsheh
2025-03-24 8:45 ` Morten Brørup
2025-03-23 16:00 ` Stephen Hemminger
2025-03-24 7:37 ` Raslan Darawsheh
2025-03-23 16:39 ` Thomas Monjalon
2025-03-24 7:38 ` Raslan Darawsheh [this message]
2025-03-24 8:50 ` [PATCH v2] " Raslan Darawsheh
2025-03-24 9:04 ` Morten Brørup
2025-03-24 9:40 ` Raslan Darawsheh
2025-03-24 9:33 ` [PATCH v3] " Raslan Darawsheh
2025-03-24 13:18 ` Morten Brørup
2025-03-24 16:59 ` Thomas Monjalon
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=CH3PR12MB846087E8B2CE0A1A443C9903CFA42@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=haijie1@huawei.com \
--cc=thomas@monjalon.net \
/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).