linux-kernel - Re: [PATCH bpf-next v2 0/2] bpf: Allow invoking kfuncs from BPF_PROG_TYPE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 05 Apr 2024 18:00:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: David Vernet <void@...ifault.com>
Cc: bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
 andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org,
 yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
 sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
 linux-kernel@...r.kernel.org, kernel-team@...a.com
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Allow invoking kfuncs from
 BPF_PROG_TYPE_SYSCALL progs

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:

On Fri,  5 Apr 2024 09:30:39 -0500 you wrote:
> Currently, a set of core BPF kfuncs (e.g. bpf_task_*, bpf_cgroup_*,
> bpf_cpumask_*, etc) cannot be invoked from BPF_PROG_TYPE_SYSCALL
> programs. The whitelist approach taken for enabling kfuncs makes sense:
> it not safe to call these kfuncs from every program type. For example,
> it may not be safe to call bpf_task_acquire() in an fentry to
> free_task().
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: Allow invoking kfuncs from BPF_PROG_TYPE_SYSCALL progs
    https://git.kernel.org/bpf/bpf-next/c/a8e03b6bbb2c
  - [bpf-next,v2,2/2] selftests/bpf: Verify calling core kfuncs from BPF_PROG_TYPE_SYCALL
    https://git.kernel.org/bpf/bpf-next/c/1bc724af00cc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html