From: patchwork-bot+netdevbpf@kernel.org
To: Ren Wei <weir@nebusec.ai>
Cc: netdev@vger.kernel.org, edumazet@kernel.org, dsahern@kernel.org,
idosch@nvidia.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, joe@wand.net.nz,
ast@kernel.org, kafai@fb.com, vega@nebusec.ai, fmancera@suse.de,
petalzu987@gmail.com
Subject: Re: [PATCH net v3 0/1] ipv6: defrag: orphan skb before queuing
Date: Fri, 16 Oct 2026 01:40:06 +0000 [thread overview]
Message-ID: <179211480676.6630.7305268106492377922.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1791008591.git.petalzu987@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Oct 2026 00:52:30 +0800 you wrote:
> From: Zixuan Chai <petalzu987@gmail.com>
>
> Hi Linux kernel maintainers,
>
> We found and validated an issue in net/ipv6/reassembly.c. The reproducer
> requires root in the initial namespace to configure TC ingress BPF socket
> assignment; fragmented IPv6 traffic received through that configuration
> triggers the crash.
>
> [...]
Here is the summary with links:
- [net,v3,1/1] ipv6: defrag: orphan skb before queuing
https://git.kernel.org/netdev/net/c/5dfa91a5ec53
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-16 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 16:52 [PATCH net v3 0/1] ipv6: defrag: orphan skb before queuing Ren Wei
2026-10-08 16:52 ` [PATCH net v3 1/1] " Ren Wei
2026-10-08 16:55 ` [PATCH net v3 0/1] " netdev-bot+sinfo
2026-10-16 1:40 ` patchwork-bot+netdevbpf [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=179211480676.6630.7305268106492377922.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=joe@wand.net.nz \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petalzu987@gmail.com \
--cc=vega@nebusec.ai \
--cc=weir@nebusec.ai \
/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