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>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Emil Tsalapatis" <emil@etsalapatis.com>,
"Nicholas Carlini" <npc@anthropic.com>, <kkd@meta.com>,
<kernel-team@meta.com>
Subject: Re: [PATCH bpf-next v1 0/2] Fix global subprog verification context
Date: Sat, 05 Sep 2026 06:33:07 +0200 [thread overview]
Message-ID: <DL73OLDDW2OX.3JGCQEAM6JO1Y@gmail.com> (raw)
In-Reply-To: <20260905034018.2095649-1-memxor@gmail.com>
On Sat Sep 5, 2026 at 5:40 AM 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 cause verifier's safety assumptions to
> be violated. Implement a fix by performing verification twice but only
> if different contexts are exercised, and add selftests to ensure coverage.
>
> Kumar Kartikeya Dwivedi (2):
> bpf: Verify global subprogs in each sleepability context
> selftests/bpf: Test global subprog callback contexts
>
CI failure in GCC-BPF run looks unrelated.
prev parent reply other threads:[~2026-09-05 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 3:40 [PATCH bpf-next v1 0/2] Fix global subprog verification context Kumar Kartikeya Dwivedi
2026-09-05 3:40 ` [PATCH bpf-next v1 1/2] bpf: Verify global subprogs in each sleepability context Kumar Kartikeya Dwivedi
2026-09-05 3:54 ` sashiko-bot
2026-09-05 4:39 ` bot+bpf-ci
2026-09-05 3:40 ` [PATCH bpf-next v1 2/2] selftests/bpf: Test global subprog callback contexts Kumar Kartikeya Dwivedi
2026-09-05 4:39 ` bot+bpf-ci
2026-09-05 4:33 ` Kumar Kartikeya Dwivedi [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=DL73OLDDW2OX.3JGCQEAM6JO1Y@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=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.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