From: Fernando Fernandez Mancera <fmancera@suse.de>
To: Hao Long <me@imlonghao.com>, netdev <netdev@vger.kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [BUG] Kernel Panic in iptfs_reassem_cont when handling large packets
Date: Tue, 3 Mar 2026 13:05:39 +0100 [thread overview]
Message-ID: <1076098b-af73-404f-a490-080dfaf59909@suse.de> (raw)
In-Reply-To: <DGRCO9SL0T5U.JTINSHJQ9KPK@imlonghao.com>
On 3/1/26 10:49 AM, Hao Long wrote:
> Hello,
>
> Recently I set up a strongSwan tunnel in AGGFRAG mode[1] in order to see
> how it fragments large packets.
>
> Later I found out the receiver node will kernel panic when handling
> large packets, I tested in different distro and both panic.
>
> Tested environment:
> - Arch Linux 6.18.13-arch1-1 strongswan-6.0.4-2
> - Arch Linux 7.0.0-rc1-1-mainline strongswan-6.0.4-2
> - NixOS 6.18.13 strongswan-6.0.4
>
> Step to reproduce:
> 1. install strongSwan and create tunnel interface in vm1, see the
> attachment init_env.sh
> 2. do step1 in vm2, but remember to switch local_addrs and remote_addrs,
> also the ip assignment
> 3. run `ping -s 3333 10.0.1.2` in vm1, 10.0.1.2 is the ip from vm2
> 4. kernel panic in vm2
>
I have reproduced this. I will send a patch a shortly so you can test it
in your environment too.
Thanks,
Fernando.
> I'm not familiar in C programming and kernel developing, so sorry I can't
> provide a useful root case analyze and a fix.
>
> Regards,
> Hao Long
>
> [1] https://docs.strongswan.org/docs/latest/features/iptfs.html
>
prev parent reply other threads:[~2026-03-03 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 9:49 [BUG] Kernel Panic in iptfs_reassem_cont when handling large packets Hao Long
2026-03-02 8:12 ` Steffen Klassert
2026-03-04 14:00 ` Christian Hopps
2026-03-03 12:05 ` Fernando Fernandez Mancera [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=1076098b-af73-404f-a490-080dfaf59909@suse.de \
--to=fmancera@suse.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=me@imlonghao.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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