[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<176772900932.2120849.10780715204750127993.git-patchwork-notify@kernel.org>
Date: Tue, 06 Jan 2026 19:50:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Toke Høiland-Jørgensen <toke@...hat.com>@codeaurora.org
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, davem@...emloft.net,
kuba@...nel.org, hawk@...nel.org, dddddd@...t.edu.cn, M202472210@...t.edu.cn,
edumazet@...gle.com, pabeni@...hat.com, horms@...nel.org,
bpf@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH bpf 1/2] bpf,
test_run: Subtract size of xdp_frame from allowed metadata size
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Mon, 5 Jan 2026 12:47:45 +0100 you wrote:
> The xdp_frame structure takes up part of the XDP frame headroom,
> limiting the size of the metadata. However, in bpf_test_run, we don't
> take this into account, which makes it possible for userspace to supply
> a metadata size that is too large (taking up the entire headroom).
>
> If userspace supplies such a large metadata size in live packet mode,
> the xdp_update_frame_from_buff() call in xdp_test_run_init_page() call
> will fail, after which packet transmission proceeds with an
> uninitialised frame structure, leading to the usual Bad Stuff.
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf, test_run: Subtract size of xdp_frame from allowed metadata size
https://git.kernel.org/bpf/bpf/c/e558cca21779
- [bpf,2/2] selftests/bpf: Update xdp_context_test_run test to check maximum metadata size
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists