[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <167903101786.26830.4703373832959381961.git-patchwork-notify@kernel.org>
Date: Fri, 17 Mar 2023 05:30:17 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, maciej.fijalkowski@...el.com,
larysa.zaremba@...el.com, toke@...hat.com, iii@...ux.ibm.com,
song@...nel.org, hawk@...nel.org, kuba@...nel.org,
bpf@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next 0/2] double-fix bpf_test_run + XDP_PASS recycling
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Thu, 16 Mar 2023 18:50:49 +0100 you wrote:
> Enabling skb PP recycling revealed a couple issues in the bpf_test_run
> code. Recycling broke the assumption that the headroom won't ever be
> touched during the test_run execution: xdp_scrub_frame() invalidates the
> XDP frame at the headroom start, while neigh xmit code overwrites 2 bytes
> to the left of the Ethernet header. The first makes the kernel panic in
> certain cases, while the second breaks xdp_do_redirect selftest on BE.
> test_run is a limited-scope entity, so let's hope no more corner cases
> will happen here or at least they will be as easy and pleasant to fix
> as those two.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf, test_run: fix crashes due to XDP frame overwriting/corruption
https://git.kernel.org/bpf/bpf-next/c/e5995bc7e2ba
- [bpf-next,2/2] selftests/bpf: fix "metadata marker" getting overwritten by the netstack
https://git.kernel.org/bpf/bpf-next/c/5640b6d89434
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