DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Aarnav JP <ajp@marvell.com>
To: <dev@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Fan Zhang <fanzhang.oss@gmail.com>
Cc: <jerinj@marvell.com>, <ndabilpuram@marvell.com>,
	<rbhansali@marvell.com>,  Aarnav JP <ajp@marvell.com>,
	<stable@dpdk.org>
Subject: [PATCH] test: fix 5-fragment IP reassembly test vectors
Date: Thu, 17 Sep 2026 11:49:02 +0530	[thread overview]
Message-ID: <20260917061902.1299400-1-ajp@marvell.com> (raw)

Fix UDP source port bytes (0x80 -> 0x08) in IPv4
and IPv6 first fragments, and fix IPv6 full packet
next_header field (0x2c -> 0x11) to indicate UDP
instead of Fragment header.

Fixes: a310577766d6 ("test/security: add inline IPsec reassembly cases")

Cc: stable@dpdk.org
Signed-off-by: Aarnav JP <ajp@marvell.com>
---
 app/test/test_security_inline_proto_vectors.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/app/test/test_security_inline_proto_vectors.h b/app/test/test_security_inline_proto_vectors.h
index 86dfa54777..b2566654e9 100644
--- a/app/test/test_security_inline_proto_vectors.h
+++ b/app/test/test_security_inline_proto_vectors.h
@@ -217,7 +217,7 @@ struct ip_reassembly_test_packet pkt_ipv6_udp_p3 = {
 	.l4_offset = 40,
 	.data = {
 		/* IP */
-		0x60, 0x00, 0x00, 0x00, 0x16, 0x6e, 0x2c, 0x40,
+		0x60, 0x00, 0x00, 0x00, 0x16, 0x6e, 0x11, 0x40,
 		0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
 		0x00, 0x00, 0xff, 0xff, 0x0d, 0x00, 0x00, 0x02,
 		0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
@@ -241,7 +241,7 @@ struct ip_reassembly_test_packet pkt_ipv6_udp_p3_f1 = {
 		0x11, 0x00, 0x00, 0x01, 0x65, 0xcf, 0x5a, 0xae,
 
 		/* UDP */
-		0x80, 0x00, 0x27, 0x10, 0x16, 0x6e, 0x2f, 0x99,
+		0x08, 0x00, 0x27, 0x10, 0x16, 0x6e, 0x2f, 0x99,
 	},
 };
 
@@ -439,7 +439,7 @@ struct ip_reassembly_test_packet pkt_ipv4_udp_p3_f1 = {
 		0x02, 0x00, 0x00, 0x02,
 
 		/* UDP */
-		0x80, 0x00, 0x27, 0x10, 0x16, 0x82, 0xbb, 0xfd,
+		0x08, 0x00, 0x27, 0x10, 0x16, 0x82, 0xbb, 0xfd,
 	},
 };
 
-- 
2.43.0


             reply	other threads:[~2026-09-17  6:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  6:19 Aarnav JP [this message]
2026-09-24 11:53 ` [PATCH] test: fix 5-fragment IP reassembly test vectors Akhil Goyal

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=20260917061902.1299400-1-ajp@marvell.com \
    --to=ajp@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=rbhansali@marvell.com \
    --cc=stable@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