From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, sammiee5311@gmail.com,
simon@swine.de
Subject: Re: [PATCHv2 bpf-next 0/2] bpf: Disable private stacks for uprobe programs
Date: Fri, 06 Nov 2026 17:50:09 +0000 [thread overview]
Message-ID: <179398740917.777046.9211090722200142386.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106164043.546879-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 6 Nov 2026 17:40:41 +0100 you wrote:
> hi,
> uprobe programs can be preempted and re-entered on the same CPU. Since
> the private stack is shared per program and CPU, a nested invocation can
> overwrite the preempted invocation's stack.
>
> This patch disables private stacks for KPROBE programs except kprobe multi
> and kprobe-session programs, identified by the BPF_TRACE_KPROBE_MULTI and
> BPF_TRACE_KPROBE_SESSION attach types. Standard kprobes lack an attach type,
> and uprobes use different attach types or none, so they run without private
> stacks.
>
> [...]
Here is the summary with links:
- [PATCHv2,bpf-next,1/2] bpf: Reject multi kprobe programs in perf event attach
https://git.kernel.org/bpf/bpf-next/c/6a6beb501ee7
- [PATCHv2,bpf-next,2/2] bpf: Disable private stacks for untagged kprobe programs
https://git.kernel.org/bpf/bpf-next/c/0eaeda0d2075
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-11-06 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 16:40 [PATCHv2 bpf-next 0/2] bpf: Disable private stacks for uprobe programs Jiri Olsa
2026-11-06 16:40 ` [PATCHv2 bpf-next 1/2] bpf: Reject multi kprobe programs in perf event attach Jiri Olsa
2026-11-06 16:40 ` [PATCHv2 bpf-next 2/2] bpf: Disable private stacks for untagged kprobe programs Jiri Olsa
2026-11-06 17:02 ` sashiko-bot
2026-11-06 17:17 ` bot+bpf-ci
2026-11-06 17: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=179398740917.777046.9211090722200142386.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=jolsa@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sammiee5311@gmail.com \
--cc=simon@swine.de \
--cc=song@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox