From: Stephen Hemminger <stephen@networkplumber.org>
To: Samyak Jain <samyak.jain@amantyatech.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Vikash kumar <vikash.kumar@amantyatech.com>,
Ankur Bharadwaj <ankur.bharadwaj@amantyatech.com>
Subject: Re: Question regarding duplicate fragment handling in DPDK IP reassembly library
Date: Mon, 15 Jun 2026 10:37:52 -0700 [thread overview]
Message-ID: <20260615103752.6155db47@phoenix.local> (raw)
In-Reply-To: <PN4PR01MB114326CC09306DA93ABA7C2ECEEE62@PN4PR01MB11432.INDPRD01.PROD.OUTLOOK.COM>
On Mon, 15 Jun 2026 12:39:48 +0000
Samyak Jain <samyak.jain@amantyatech.com> wrote:
> Hi DPDK Community,
>
> I am using DPDK 25.11 and evaluating the IP reassembly library
> (librte_ip_frag).
>
> During testing, I observed that duplicate fragments appear to cause reassembly failure and the fragment context gets invalidated.
>
> I would like to know:
>
> 1. Is duplicate fragment handling intentionally unsupported in
> rte_ipv4_frag_reassemble_packet() / rte_ipv6_frag_reassemble_packet()?
>
> 2. Has there been any upstream discussion or patch to support
> duplicate fragments while still rejecting conflicting
> fragments?
>
> 3. Are there any recommended approaches for applications that need
> Linux-like duplicate fragment tolerance?
>
> Any guidance would be appreciated.
>
> Thanks & Regards,
> Samyak Jain
>
Short answer: yes it is buggy, no it shouldn't be.
Looking into it but not a simple answer
prev parent reply other threads:[~2026-06-15 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 12:39 Question regarding duplicate fragment handling in DPDK IP reassembly library Samyak Jain
2026-06-15 17:37 ` Stephen Hemminger [this message]
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=20260615103752.6155db47@phoenix.local \
--to=stephen@networkplumber.org \
--cc=ankur.bharadwaj@amantyatech.com \
--cc=dev@dpdk.org \
--cc=samyak.jain@amantyatech.com \
--cc=vikash.kumar@amantyatech.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