All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Zhiling Zou <zhilinz@nebusec.ai>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, ast@kernel.org,
	daniel@iogearbox.net, davem@davemloft.net, kuba@kernel.org,
	hawk@kernel.org, john.fastabend@gmail.com, sdf@fomichev.me,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	liuhangbin@gmail.com, kafai@fb.com, toke@redhat.com,
	vega@nebusec.ai
Subject: Re: [PATCH net 0/1] xdp: reject clones that overrun skb_shared_info tailroom
Date: Thu, 06 Aug 2026 16:00:05 +0000	[thread overview]
Message-ID: <178603200563.1353047.6718868638541951645.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1785757386.git.zhilinz@nebusec.ai>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon,  3 Aug 2026 20:15:31 +0800 you wrote:
> Hi Linux kernel maintainers,
> 
> We found and validated a issue in net/core/xdp.c. The bug was reproduced as
> root in the initial namespace through XDP devmap broadcast cloning.
> We've tested it, and it should not affect any other functionality.
> 
> We will provide detailed information about the bug
> in this email, along with a PoC to trigger it.
> 
> [...]

Here is the summary with links:
  - [net,1/1] xdp: reject clones that overrun skb_shared_info tailroom
    https://git.kernel.org/netdev/net/c/e48e8edbef2e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-06 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 12:15 [PATCH net 0/1] xdp: reject clones that overrun skb_shared_info tailroom Zhiling Zou
2026-08-03 12:15 ` [PATCH net 1/1] " Zhiling Zou
2026-08-04 12:16   ` sashiko-bot
2026-08-04 12:54     ` zhilin zou
2026-08-06 16:00 ` 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=178603200563.1353047.6718868638541951645.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kuba@kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=toke@redhat.com \
    --cc=vega@nebusec.ai \
    --cc=zhilinz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.