From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, memxor@gmail.com, puranjay@kernel.org,
shakeel.butt@linux.dev, mykyta.yatsenko5@gmail.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next v7 0/3] bpf: Implement stack_map_get_build_id_offset_sleepable()
Date: Thu, 28 May 2026 22:00:09 +0000 [thread overview]
Message-ID: <178000560988.1528587.15711081709424255341.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260525223948.1920986-1-ihor.solodrai@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 25 May 2026 15:39:45 -0700 you wrote:
> The series introduces stack_map_get_build_id_offset_sleepable(),
> fixing a gap with parsing build_id in sleepable context in stackmap.c
>
> In particular, this fixes a deadlock in
> stack_map_get_build_id_offset() doing a blocking __kernel_read(),
> which happens since commit 777a8560fd29 ("lib/buildid: use
> __kernel_read() for sleepable context").
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/3] bpf: Factor out stack_map build ID helpers
https://git.kernel.org/bpf/bpf-next/c/fc99547a8bda
- [bpf-next,v7,2/3] bpf: Avoid faultable build ID reads under mm locks
https://git.kernel.org/bpf/bpf-next/c/fad3021faf7b
- [bpf-next,v7,3/3] bpf: Cache build IDs in sleepable stackmap path
https://git.kernel.org/bpf/bpf-next/c/5e9099d8ff24
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-05-28 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 22:39 [PATCH bpf-next v7 0/3] bpf: Implement stack_map_get_build_id_offset_sleepable() Ihor Solodrai
2026-05-25 22:39 ` [PATCH bpf-next v7 1/3] bpf: Factor out stack_map build ID helpers Ihor Solodrai
2026-05-25 23:11 ` sashiko-bot
2026-05-28 21:57 ` Andrii Nakryiko
2026-06-03 23:10 ` Ihor Solodrai
2026-05-25 23:17 ` bot+bpf-ci
2026-05-25 22:39 ` [PATCH bpf-next v7 2/3] bpf: Avoid faultable build ID reads under mm locks Ihor Solodrai
2026-05-25 22:39 ` [PATCH bpf-next v7 3/3] bpf: Cache build IDs in sleepable stackmap path Ihor Solodrai
2026-05-28 21:57 ` Andrii Nakryiko
2026-05-28 22:00 ` 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=178000560988.1528587.15711081709424255341.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=puranjay@kernel.org \
--cc=shakeel.butt@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.