From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, ctao@meta.com
Subject: Re: [PATCH bpf-next v4 0/2] bpf: copy BPF token from main program to subprograms
Date: Thu, 16 Apr 2026 00:12:20 +0000 [thread overview]
Message-ID: <177629834053.2488030.556653357025366202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260415-subprog-token-fix-v4-0-9bd000e8b068@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 15 Apr 2026 13:03:54 -0700 you wrote:
> bpf_jit_subprogs() omits aux->token when it creates a struct
> bpf_prog_aux instances for a subprograms.
> This means that for programs loaded via BPF token (i.e., from a
> non-init user namespace), subprograms fail the bpf_token_capable()
> check in bpf_prog_kallsyms_add() and don't appear in /proc/kallsyms.
> Which in-turn makes it impossible to freplace such subprograms.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/2] bpf: copy BPF token from main program to subprograms
https://git.kernel.org/bpf/bpf/c/0251e40c4829
- [bpf-next,v4,2/2] selftests/bpf: verify kallsyms entries for token-loaded subprograms
https://git.kernel.org/bpf/bpf/c/969fb456ffb4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-16 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 20:03 [PATCH bpf-next v4 0/2] bpf: copy BPF token from main program to subprograms Eduard Zingerman
2026-04-15 20:03 ` [PATCH bpf-next v4 1/2] " Eduard Zingerman
2026-04-15 20:03 ` [PATCH bpf-next v4 2/2] selftests/bpf: verify kallsyms entries for token-loaded subprograms Eduard Zingerman
2026-04-16 0:12 ` patchwork-bot+netdevbpf [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=177629834053.2488030.556653357025366202.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ctao@meta.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yonghong.song@linux.dev \
/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