From: patchwork-bot+netdevbpf@kernel.org
To: Sanghyun Park <sanghyun.park.cnu@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, sun.jian.kdev@gmail.com, puranjay@kernel.org,
ihor.solodrai@linux.dev, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, bigeasy@linutronix.de,
clrkwllms@kernel.org, rostedt@goodmis.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
syzbot+cdd6c0925e12b0af60cc@syzkaller.appspotmail.com,
sashiko-bot@kernel.org
Subject: Re: [PATCH bpf-next v3] bpf: Fix mmap_lock leak in irq_work path
Date: Fri, 07 Aug 2026 22:50:17 +0000 [thread overview]
Message-ID: <178614301790.2448714.12103864417505840837.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260805031425.2157475-2-sanghyun.park.cnu@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
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
prev parent reply other threads:[~2026-08-07 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 3:14 [PATCH bpf-next v3] bpf: Fix mmap_lock leak in irq_work path Sanghyun Park
2026-08-05 4:56 ` bot+bpf-ci
2026-08-07 22:50 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178614301790.2448714.12103864417505840837.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=clrkwllms@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sanghyun.park.cnu@gmail.com \
--cc=sashiko-bot@kernel.org \
--cc=song@kernel.org \
--cc=sun.jian.kdev@gmail.com \
--cc=syzbot+cdd6c0925e12b0af60cc@syzkaller.appspotmail.com \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.