From: Christian Simon <simon@swine.de>
To: bpf@vger.kernel.org
Cc: Christian Simon <simon@swine.de>,
ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, tj@kernel.org, yonghong.song@linux.dev,
stable@vger.kernel.org, andrii.nakryiko@gmail.com,
olsajiri@gmail.com
Subject: [PATCH bpf v3 0/2] disable private stack for sleepable programs
Date: Sat, 22 Aug 2026 23:54:42 +0100 [thread overview]
Message-ID: <20260822225444.2774461-1-simon@swine.de> (raw)
A JITed BPF program can use one private stack per program and CPU.
Sleepable programs can be preempted, allowing another task to run the
same program on the same CPU. The second invocation then reuses and can
overwrite the first invocation's private stack.
This patch series disables private stacks for sleepable programs and
adds a selftest covering that stack corruption.
---
Changes in v3:
- Target sleepable only.
- Add the powerpc Fixes tag.
- Split fix and selftests
v2: https://lore.kernel.org/bpf/20260818203234.1142913-1-simon@swine.de/
Christian Simon (2):
bpf: disable private stack for sleepable programs
selftests/bpf: verify preemptible uprobes avoid private stack
kernel/bpf/verifier.c | 9 +
.../bpf/prog_tests/uprobe_sleepable_stack.c | 165 ++++++++++++++++++
.../bpf/progs/uprobe_sleepable_stack.c | 89 ++++++++++
3 files changed, 263 insertions(+)
create mode 100644 tools/testing/selftests/bpf/prog_tests/uprobe_sleepable_stack.c
create mode 100644 tools/testing/selftests/bpf/progs/uprobe_sleepable_stack.c
base-commit: 75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7
--
2.54.0
next reply other threads:[~2026-08-22 22:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 22:54 Christian Simon [this message]
2026-08-22 22:54 ` [PATCH bpf v3 1/2] bpf: disable private stack for sleepable programs Christian Simon
2026-08-22 23:10 ` sashiko-bot
2026-08-22 23:46 ` bot+bpf-ci
2026-08-26 1:20 ` Alexei Starovoitov
2026-08-26 13:11 ` Jiri Olsa
2026-08-27 14:56 ` Andrii Nakryiko
2026-08-27 16:35 ` Alexei Starovoitov
2026-08-27 16:40 ` Andrii Nakryiko
2026-08-27 16:55 ` Alexei Starovoitov
2026-08-27 22:32 ` Jiri Olsa
2026-08-22 22:54 ` [PATCH bpf v3 2/2] selftests/bpf: verify preemptible uprobes avoid private stack Christian Simon
2026-08-22 23:05 ` sashiko-bot
2026-08-22 23:58 ` bot+bpf-ci
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=20260822225444.2774461-1-simon@swine.de \
--to=simon@swine.de \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=martin.lau@kernel.org \
--cc=olsajiri@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tj@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