From: Josh Poimboeuf <jpoimboe@kernel.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
bpf@vger.kernel.org,
Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>,
Petr Mladek <pmladek@suse.com>, Song Liu <song@kernel.org>,
Raja Khan <raja.khan@crowdstrike.com>,
Miroslav Benes <mbenes@suse.cz>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH v2 0/2] bpf, x86/unwind/orc: Support reliable unwinding through BPF stack frames
Date: Wed, 3 Dec 2025 19:32:14 -0800 [thread overview]
Message-ID: <cover.1764818927.git.jpoimboe@kernel.org> (raw)
Fix livepatch stalls which may be seen when a task is blocked with BPF
JIT on its kernel stack.
Changes since v1 (https://lore.kernel.org/cover.1764699074.git.jpoimboe@kernel.org):
- fix NULL ptr deref in __arch_prepare_bpf_trampoline()
Josh Poimboeuf (2):
bpf: Add bpf_has_frame_pointer()
x86/unwind/orc: Support reliable unwinding through BPF stack frames
arch/x86/kernel/unwind_orc.c | 39 +++++++++++++++++++++++++-----------
arch/x86/net/bpf_jit_comp.c | 12 +++++++++++
include/linux/bpf.h | 3 +++
kernel/bpf/core.c | 16 +++++++++++++++
4 files changed, 58 insertions(+), 12 deletions(-)
--
2.51.1
next reply other threads:[~2025-12-04 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 3:32 Josh Poimboeuf [this message]
2025-12-04 3:32 ` [PATCH v2 1/2] bpf: Add bpf_has_frame_pointer() Josh Poimboeuf
2025-12-04 14:04 ` Jiri Olsa
2025-12-04 17:02 ` Josh Poimboeuf
2025-12-04 3:32 ` [PATCH v2 2/2] x86/unwind/orc: Support reliable unwinding through BPF stack frames Josh Poimboeuf
2025-12-04 14:27 ` [PATCH v2 0/2] bpf, " Jiri Olsa
2025-12-10 7:40 ` patchwork-bot+netdevbpf
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=cover.1764818927.git.jpoimboe@kernel.org \
--to=jpoimboe@kernel.org \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=raja.khan@crowdstrike.com \
--cc=song@kernel.org \
--cc=x86@kernel.org \
/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.