Re: [PATCH bpf-next v3] bpf: Fix mmap_lock leak in irq_work path
| Newsgroups | dev.linux.lists.linux-rt-devel,org.kernel.vger.bpf,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178614301790.2448714.12103864417505840837.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to bpf/bpf-next.git (master) by Andrii Nakryiko <[email protected]>: On Wed, 5 Aug 2026 12:14:25 +0900 you wrote: > stack_map_get_build_id_offset() introduced a per-CPU irq_work to defer > mmap_read_unlock() from NMI context, and bpf_find_vma() later reused the > same mmap_unlock_work. Both callers only check whether the work is busy > before taking mmap_lock, so a nested caller can reuse the slot before the > first caller queues it. Two read locks may then be acquired while only one > deferred unlock runs, leaking a read lock and blocking exit_mmap(). > > [...] Here is the summary with links: - [bpf-next,v3] bpf: Fix mmap_lock leak in irq_work path https://git.kernel.org/bpf/bpf-next/c/51476f6a06ef You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html