From: Eduard Zingerman <eddyz87@gmail.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Emil Tsalapatis <emil@etsalapatis.com>,
Nicholas Carlini <npc@anthropic.com>,
kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf v3 0/2] Fix global subprog verification context
Date: Tue, 15 Sep 2026 00:51:20 -0700 [thread overview]
Message-ID: <e82dfcb535313ba346680f8636d25b5f6b199bfc.camel@gmail.com> (raw)
In-Reply-To: <DLF2OAEKW80O.1BVYORL67XIKU@gmail.com>
On Mon, 2026-09-14 at 15:27 +0200, Kumar Kartikeya Dwivedi wrote:
> On Mon Sep 14, 2026 at 3:19 PM CEST, Kumar Kartikeya Dwivedi wrote:
> > Global subprogs can be invoked in both sleepable and non-sleepable
> > contexts, but are verified based on context assumptions for the program
> > type as a whole and not the precise context in which they are invoked.
> > Nicholas identified that this can violate verifier safety assumptions.
> > Verify global subprogs once for each observed sleepability context and add
> > workqueue callback regression tests.
> >
>
> By mistake, I tagged bpf tree for this one, sorry. I can respin again after a
> round of feedback or let someone else decide to apply it to either tree, if this
> version is landable.
It applies and builds cleanly, I'd just land it in bpf.
next prev parent reply other threads:[~2026-09-15 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 13:19 [PATCH bpf v3 0/2] Fix global subprog verification context Kumar Kartikeya Dwivedi
2026-09-14 13:19 ` [PATCH bpf v3 1/2] bpf: Verify global subprogs in each sleepability context Kumar Kartikeya Dwivedi
2026-09-15 7:50 ` Eduard Zingerman
2026-09-14 13:19 ` [PATCH bpf v3 2/2] selftests/bpf: Test global subprog callback contexts Kumar Kartikeya Dwivedi
2026-09-14 13:27 ` [PATCH bpf v3 0/2] Fix global subprog verification context Kumar Kartikeya Dwivedi
2026-09-15 7:51 ` Eduard Zingerman [this message]
2026-09-16 17:00 ` 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=e82dfcb535313ba346680f8636d25b5f6b199bfc.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--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 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.