From: Stephen Hemminger <stephen@networkplumber.org>
To: <skori@marvell.com>
Cc: Jie Hai <haijie1@huawei.com>, <dev@dpdk.org>
Subject: Re: [PATCH 1/2] net: fix offset calculation for GENEVE packet
Date: Tue, 20 May 2025 14:21:37 -0700 [thread overview]
Message-ID: <20250520142137.366c8235@hermes.local> (raw)
In-Reply-To: <20250519160711.4024414-1-skori@marvell.com>
On Mon, 19 May 2025 21:36:55 +0530
<skori@marvell.com> wrote:
> From: Sunil Kumar Kori <skori@marvell.com>
>
> While parsing packet headers, offset must be added to get next
> header but for geneve header parsing offset is overwritten.
> Also inner_l2_len is not set in case of geneve packets.
>
> Fixes: 64ed7f854cf4 ("net: add tunnel packet type parsing")
>
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
Looks good, but why reorder the assignment to *off ?
Could just be:
diff --git a/lib/net/rte_net.c b/lib/net/rte_net.c
index be24690fdf..cdad463398 100644
--- a/lib/net/rte_net.c
+++ b/lib/net/rte_net.c
@@ -252,6 +252,7 @@ ptype_tunnel_with_udp(uint16_t *proto, const struct rte_mbuf *m,
return 0;
geneve_len = sizeof(*gnh) + gnh->opt_len * 4;
*off = geneve_len;
+ hdr_lens->inner_l2_len = sizeof(struct rte_udp_hdr) + geneve_len;
*proto = gnh->proto;
if (gnh->proto == 0)
*proto = rte_cpu_to_be_16(RTE_ETHER_TYPE_IPV4);
next prev parent reply other threads:[~2025-05-20 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 16:06 skori
2025-05-19 16:06 ` [PATCH 2/2] app/testpmd: clear stale internal len information skori
2025-05-20 21:17 ` Stephen Hemminger
2025-05-21 5:01 ` [EXTERNAL] " Sunil Kumar Kori
2025-05-21 5:11 ` [PATCH v2 1/2] net: fix offset calculation for GENEVE packet skori
2025-05-21 5:11 ` [PATCH v2 2/2] app/testpmd: clear stale internal len information skori
2025-05-21 9:33 ` [PATCH v2 1/2] net: fix offset calculation for GENEVE packet huangdengdui
2025-05-20 21:21 ` Stephen Hemminger [this message]
2025-05-21 4:57 ` [EXTERNAL] Re: [PATCH " Sunil Kumar Kori
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=20250520142137.366c8235@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=haijie1@huawei.com \
--cc=skori@marvell.com \
/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).