From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
kkd@meta.com, kernel-team@meta.com
Subject: [PATCH bpf v1 0/2] Fix bpf_link grace period wait for tracepoints
Date: Mon, 30 Mar 2026 05:21:21 +0200 [thread overview]
Message-ID: <20260330032124.3141001-1-memxor@gmail.com> (raw)
A recent change to non-faultable tracepoints switched from
preempt-disabled critical sections to SRCU-fast, which breaks
assumptions in the bpf_link_free() path. Use call_srcu() to fix the
breakage. While at it, retire rcu_trace_implies_rcu_gp() and clean up
all in-tree users.
Kumar Kartikeya Dwivedi (2):
bpf: Fix grace period wait for tracepoint bpf_link
bpf: Retire rcu_trace_implies_rcu_gp()
include/linux/rcupdate.h | 12 ------------
include/linux/tracepoint.h | 8 ++++++++
kernel/bpf/core.c | 10 ++++------
kernel/bpf/memalloc.c | 33 ++++++++++---------------------
kernel/bpf/syscall.c | 40 ++++++++++++++++++++++----------------
5 files changed, 45 insertions(+), 58 deletions(-)
base-commit: c369299895a591d96745d6492d4888259b004a9e
--
2.52.0
next reply other threads:[~2026-03-30 3:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 3:21 Kumar Kartikeya Dwivedi [this message]
2026-03-30 3:21 ` [PATCH bpf v1 1/2] bpf: Fix grace period wait for tracepoint bpf_link Kumar Kartikeya Dwivedi
2026-03-30 3:36 ` Kumar Kartikeya Dwivedi
2026-03-30 10:00 ` Puranjay Mohan
2026-03-30 14:03 ` Kumar Kartikeya Dwivedi
2026-03-30 9:52 ` Puranjay Mohan
2026-03-30 14:02 ` Kumar Kartikeya Dwivedi
2026-03-30 15:07 ` Steven Rostedt
2026-03-30 15:27 ` Kumar Kartikeya Dwivedi
2026-03-30 16:10 ` Steven Rostedt
2026-03-30 3:21 ` [PATCH bpf v1 2/2] bpf: Retire rcu_trace_implies_rcu_gp() Kumar Kartikeya Dwivedi
2026-03-30 10:17 ` Puranjay Mohan
2026-03-30 10:40 ` Paul E. McKenney
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=20260330032124.3141001-1-memxor@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=martin.lau@kernel.org \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox