Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Thu, 19 May 2022 15:25:32 +0100 you wrote:
> Unprivileged BPF disabled (kernel.unprivileged_bpf_disabled >= 1)
> is the default in most cases now; when set, the BPF system call is
> blocked for users without CAP_BPF/CAP_SYS_ADMIN. In some cases
> however, it makes sense to split activities between capability-requiring
> ones - such as program load/attach - and those that might not require
> capabilities such as reading perf/ringbuf events, reading or
> updating BPF map configuration etc. One example of this sort of
> approach is a service that loads a BPF program, and a user-space
> program that interacts with it.
>
> [...]
Here is the summary with links:
- [v4,bpf-next,1/2] bpf: refine kernel.unprivileged_bpf_disabled behaviour
https://git.kernel.org/bpf/bpf-next/c/c8644cd0efe7
- [v4,bpf-next,2/2] selftests/bpf: add tests verifying unprivileged bpf behaviour
https://git.kernel.org/bpf/bpf-next/c/90a039fd19fc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
