Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@xxxxxxxxxxxxx>:
On Mon, 27 May 2024 13:20:06 +0200 you wrote:
> We have seen a few syzkaller reports of locking violations triggered by
> map_delete from sockmap/sockhash from an unexpected code path, for instance
> when irqs were disabled, or during a kfree inside a map_update.
>
> The consensus is [1] to block map_delete op in the verifier for programs
> which are not allowed to update sockmap/sockhash already today, instead of
> trying to make sockmap deletes lock-safe in every possible context.
>
> [...]
Here is the summary with links:
- [bpf,1/3] bpf: Allow delete from sockmap/sockhash only if update is allowed
https://git.kernel.org/bpf/bpf/c/98e948fb60d4
- [bpf,2/3] Revert "bpf, sockmap: Prevent lock inversion deadlock in map delete elem"
https://git.kernel.org/bpf/bpf/c/3b9ce0491a43
- [bpf,3/3] selftests/bpf: Cover verifier checks for mutating sockmap/sockhash
https://git.kernel.org/bpf/bpf/c/a63bf556160f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
