[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171206882711.27281.12209723664828654389.git-patchwork-notify@kernel.org>
Date: Tue, 02 Apr 2024 14:40:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Sitnicki <jakub@...udflare.com>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, kernel-team@...udflare.com,
xrivendell7@...il.com, samsun1006219@...il.com,
syzbot+bc922f476bd65abbd466@...kaller.appspotmail.com,
syzbot+d4066896495db380182e@...kaller.appspotmail.com,
john.fastabend@...il.com, eadavis@...com, shung-hsi.yu@...e.com
Subject: Re: [PATCH bpf] bpf,
sockmap: Prevent lock inversion deadlock in map delete elem
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Tue, 2 Apr 2024 12:46:21 +0200 you wrote:
> syzkaller started using corpuses where a BPF tracing program deletes
> elements from a sockmap/sockhash map. Because BPF tracing programs can be
> invoked from any interrupt context, locks taken during a map_delete_elem
> operation must be hardirq-safe. Otherwise a deadlock due to lock inversion
> is possible, as reported by lockdep:
>
> CPU0 CPU1
>
> [...]
Here is the summary with links:
- [bpf] bpf, sockmap: Prevent lock inversion deadlock in map delete elem
https://git.kernel.org/bpf/bpf/c/ff9105993240
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