From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, memxor@gmail.com, eddyz87@gmail.com,
info@starlabs.sg, bpf@vger.kernel.org
Subject: Re: [PATCH bpf v2 1/4] bpf: Add KF_PERFMON kfunc flag
Date: Fri, 11 Sep 2026 00:00:08 +0000 [thread overview]
Message-ID: <178908480813.2150752.11899607418108450585.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910213510.49358-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 10 Sep 2026 23:35:07 +0200 you wrote:
> Tracing related BPF helpers e.g. under bpf_base_func_proto() are gated
> behind CAP_PERFMON. However, the same is currently not true for kfuncs
> and they are accessible via plain CAP_BPF. Add a new KF_PERFMON flag
> which can be used such that check_kfunc_call() ensures env->allow_ptr_leaks
> is permitted. This follows similar pattern to existing KF_DESTRUCTIVE flag.
>
> The rejection returns -EPERM to match the other CAP_PERFMON gates in the
> verifier, that is, check_ptr_to_btf_access() and check_ptr_to_map_access(),
> which report the very same policy to user space.
>
> [...]
Here is the summary with links:
- [bpf,v2,1/4] bpf: Add KF_PERFMON kfunc flag
https://git.kernel.org/bpf/bpf/c/88ce88e933e4
- [bpf,v2,2/4] bpf: Require CAP_PERFMON for kfuncs reading memory
https://git.kernel.org/bpf/bpf/c/81c975aae375
- [bpf,v2,3/4] bpf: Require CAP_PERFMON for untrusted read-only memory reads
https://git.kernel.org/bpf/bpf/c/f9191460cd80
- [bpf,v2,4/4] selftests/bpf: Add tests for the KF_PERFMON gates
https://git.kernel.org/bpf/bpf/c/a903f145a891
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-09-11 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 21:35 [PATCH bpf v2 1/4] bpf: Add KF_PERFMON kfunc flag Daniel Borkmann
2026-09-10 21:35 ` [PATCH bpf v2 2/4] bpf: Require CAP_PERFMON for kfuncs reading memory Daniel Borkmann
2026-09-10 21:45 ` sashiko-bot
2026-09-10 22:33 ` bot+bpf-ci
2026-09-10 21:35 ` [PATCH bpf v2 3/4] bpf: Require CAP_PERFMON for untrusted read-only memory reads Daniel Borkmann
2026-09-10 22:33 ` bot+bpf-ci
2026-09-10 21:35 ` [PATCH bpf v2 4/4] selftests/bpf: Add tests for the KF_PERFMON gates Daniel Borkmann
2026-09-10 22:33 ` bot+bpf-ci
2026-09-11 0:00 ` 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=178908480813.2150752.11899607418108450585.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=info@starlabs.sg \
--cc=memxor@gmail.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