From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: Amery Hung <ameryhung@gmail.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
Nicholas Carlini <npc@anthropic.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH bpf v1 0/4] bpf: Scope callback arguments to their frame
Date: Fri, 6 Nov 2026 16:32:15 -0700 [thread overview]
Message-ID: <2785198b-ca41-4cee-9dba-bc0c1e6e8f25@linux.dev> (raw)
In-Reply-To: <20261106231157.2840635-1-ihor.solodrai@linux.dev>
On 11/6/26 4:11 PM, Ihor Solodrai wrote:
> [...]
>
> Ihor Solodrai (4):
> bpf: Scope the bpf_user_ringbuf_drain() dynptr to its callback frame
> selftests/bpf: Cover the user ringbuf callback dynptr lifetime
> bpf: Scope the bpf_for_each_map_elem() array key to the callback frame
> selftests/bpf: Cover callback-frame map key lifetime
Alexei, if this lands first, your pending verifier rewrite will need a
hunk like the one pasted below. Or the other way around.
Without it, a join can link a value to the wrong callback frame.
diff --git a/kernel/bpf/join.c b/kernel/bpf/join.c
index cc4494aef187..92b94e18c873 100644
--- a/kernel/bpf/join.c
+++ b/kernel/bpf/join.c
@@ -464,6 +464,9 @@ static bool join_func(struct bpf_join_state *js, struct bpf_func_state *fd,
return false;
if (!join_loop_stack(fa, fb))
return false;
+ jid_note(js, fa->frame_id, fb->frame_id, true);
+ } else if (!jid_strict_ok(js, fa->frame_id, fb->frame_id)) {
+ return false;
}
for (i = 0; i < MAX_BPF_REG; i++) {
>
> include/linux/bpf.h | 2 +
> include/linux/bpf_verifier.h | 2 +
> kernel/bpf/arraymap.c | 19 ++-
> kernel/bpf/states.c | 3 +
> kernel/bpf/verifier.c | 16 +++
> .../selftests/bpf/progs/user_ringbuf_fail.c | 135 ++++++++++++++++++
> .../bpf/progs/verifier_iterating_callbacks.c | 91 ++++++++++++
> 7 files changed, 266 insertions(+), 2 deletions(-)
>
>
> base-commit: 475a0cfd02f14d764023e926ac01fc7597134229
prev parent reply other threads:[~2026-11-06 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 23:11 Ihor Solodrai
2026-11-06 23:11 ` [PATCH bpf v1 1/4] bpf: Scope the bpf_user_ringbuf_drain() dynptr to its callback frame Ihor Solodrai
2026-11-06 23:11 ` [PATCH bpf v1 2/4] selftests/bpf: Cover the user ringbuf callback dynptr lifetime Ihor Solodrai
2026-11-06 23:11 ` [PATCH bpf v1 3/4] bpf: Scope the bpf_for_each_map_elem() array key to the callback frame Ihor Solodrai
2026-11-06 23:11 ` [PATCH bpf v1 4/4] selftests/bpf: Cover callback-frame map key lifetime Ihor Solodrai
2026-11-06 23:15 ` [PATCH bpf v1 0/4] bpf: Scope callback arguments to their frame Ihor Solodrai
2026-11-06 23:22 ` Kumar Kartikeya Dwivedi
2026-11-06 23:32 ` Ihor Solodrai [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=2785198b-ca41-4cee-9dba-bc0c1e6e8f25@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=npc@anthropic.com \
/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
all inboxes | Powered by JetHome®