Re: [PATCH bpf-next v2] bpf: Refuse the prologue for an extension if callers keep packet pointers

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Mon, 19 Oct 2026 01:13:27 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
> 
> An extension that writes to the packet of a tc, lwt_xmit or sk_skb program
> starts with bpf_unclone_prologue().  If the skb is cloned, that gives it
> a new head.
> 
> It does not count as changing packet data.  changes_pkt_data goes by the
> helpers and kfuncs that a program calls, and whether it gets a prologue
> is known only after it has been compared with its target.  So the extension
> can replace a global function that leaves the packet alone, and the callers
> of that function keep their packet pointers across the call.  These point
> into the old head, which is left to the other clone.  Once that is freed,
> by the reader of a packet socket for example:
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] bpf: Refuse the prologue for an extension if callers keep packet pointers
    https://git.kernel.org/bpf/bpf-next/c/4f842631f178

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