From: Christian Hopps <chopps@labn.net>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Hao Long <me@imlonghao.com>, netdev <netdev@vger.kernel.org>,
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: Wed, 4 Mar 2026 14:00:41 +0000 [thread overview]
Message-ID: <F4AA8F05-F065-480A-8F83-7D9FD730650F@labn.net> (raw)
In-Reply-To: <aaVGVTelUZ9gFhkT@secunet.com>
Steffen Klassert <steffen.klassert@secunet.com> writes:
> Add Chris, the author of IPTFS, to the Cc.
Got it, will take a look soon.
Thanks,
Chris.
> On Sun, Mar 01, 2026 at 05:49:19PM +0800, 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
next prev parent reply other threads:[~2026-03-04 14:00 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 [this message]
2026-03-03 12:05 ` Fernando Fernandez Mancera
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=F4AA8F05-F065-480A-8F83-7D9FD730650F@labn.net \
--to=chopps@labn.net \
--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