linux-kernel - Re: [PATCH bpf-next v3 0/3] Annotate kfuncs in .BTF

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] [thread-next>] [day] [month] [year] [list]

Date: Mon, 8 Jan 2024 10:15:45 +0100
From: Lorenz Bauer <lorenz.bauer@...valent.com>
To: Daniel Xu <dxu@...uu.xyz>
Cc: linux-input@...r.kernel.org, coreteam@...filter.org, 
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
	netfilter-devel@...r.kernel.org, linux-kselftest@...r.kernel.org, 
	linux-trace-kernel@...r.kernel.org, fsverity@...ts.linux.dev, 
	bpf@...r.kernel.org, netdev@...r.kernel.org, 
	linux-stm32@...md-mailman.stormreply.com, cgroups@...r.kernel.org, 
	alexei.starovoitov@...il.com, olsajiri@...il.com, quentin@...valent.com, 
	alan.maguire@...cle.com, memxor@...il.com
Subject: Re: [PATCH bpf-next v3 0/3] Annotate kfuncs in .BTF_ids section

On Sat, Jan 6, 2024 at 7:25 PM Daniel Xu <dxu@...uu.xyz> wrote:
>
> === Description ===
>
> This is a bpf-treewide change that annotates all kfuncs as such inside
> .BTF_ids. This annotation eventually allows us to automatically generate
> kfunc prototypes from bpftool.
>
> We store this metadata inside a yet-unused flags field inside struct
> btf_id_set8 (thanks Kumar!). pahole will be taught where to look.

This is great, thanks for tackling this. With yout patches we can
figure out the full set of kfuncs. Is there a way to extend it so that
we can tell which program context a kfunc can be called from?