[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174543182801.2725891.7635648941344459709.git-patchwork-notify@kernel.org>
Date: Wed, 23 Apr 2025 18:10:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Feng Yang <yangfeng59949@....com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org,
mattbobrowski@...gle.com, rostedt@...dmis.org, mhiramat@...nel.org,
mathieu.desnoyers@...icios.com, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v4] bpf: streamline allowed helpers between tracing
and base sets
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Wed, 23 Apr 2025 15:31:51 +0800 you wrote:
> From: Feng Yang <yangfeng@...inos.cn>
>
> Many conditional checks in switch-case are redundant
> with bpf_base_func_proto and should be removed.
>
> Regarding the permission checks bpf_base_func_proto:
> The permission checks in bpf_prog_load (as outlined below)
> ensure that the trace has both CAP_BPF and CAP_PERFMON capabilities,
> thus enabling the use of corresponding prototypes
> in bpf_base_func_proto without adverse effects.
> bpf_prog_load
> ......
> bpf_cap = bpf_token_capable(token, CAP_BPF);
> ......
> if (type != BPF_PROG_TYPE_SOCKET_FILTER &&
> type != BPF_PROG_TYPE_CGROUP_SKB &&
> !bpf_cap)
> goto put_token;
> ......
> if (is_perfmon_prog_type(type) && !bpf_token_capable(token, CAP_PERFMON))
> goto put_token;
> ......
>
> [...]
Here is the summary with links:
- [bpf-next,v4] bpf: streamline allowed helpers between tracing and base sets
https://git.kernel.org/bpf/bpf-next/c/6aca583f90b0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists