Re: [PATCH bpf-next v4 0/3] Annotate kfuncs in .BTF_ids section
From: Jiri Olsa <hidden>
Date: 2024-02-03 14:40:28
Also in:
bpf, cgroups, linux-arm-kernel, linux-doc, linux-input, linux-kselftest, linux-trace-kernel, lkml, netfilter-devel
Subsystem:
bpf [general] (safe dynamic programs and tools), the rest · Maintainers:
Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko, Eduard Zingerman, Kumar Kartikeya Dwivedi, Linus Torvalds
On Fri, Feb 02, 2024 at 03:09:05PM -0800, Manu Bretelle wrote:
quoted hunk ↗ jump to hunk
On Sun, Jan 28, 2024 at 06:24:05PM -0700, Daniel Xu wrote:quoted
=== 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. More details about the full chain of events are available in commit 3's description. The accompanying pahole and bpftool changes can be viewed here on these "frozen" branches [0][1]. [0]: https://github.com/danobi/pahole/tree/kfunc_btf-v3-mailed [1]: https://github.com/danobi/linux/tree/kfunc_bpftool-mailedI hit a similar issue to [0] on master 943b043aeecc ("selftests/bpf: Fix bench runner SIGSEGV") when cross-compiling on x86_64 (LE) to s390x (BE). I do have CONFIG_DEBUG_INFO_BTF enable and the issue would not trigger if I disabled CONFIG_DEBUG_INFO_BTF (and with the fix mentioned in [0]). What seems to happen is that `tools/resolve_btfids` is ran in the context of the host endianess and if I printk before the WARN_ON:diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c index ef380e546952..a9ed7a1a4936 100644 --- a/kernel/bpf/btf.c +++ b/kernel/bpf/btf.c @@ -8128,6 +8128,7 @@ int register_btf_kfunc_id_set(enum bpf_prog_type prog_type, * WARN() for initcall registrations that do not check errors. */ if (!(kset->set->flags & BTF_SET8_KFUNCS)) { + printk("Flag 0x%08X, expected 0x%08X\n", kset->set->flags, BTF_SET8_KFUNCS); WARN_ON(!kset->owner); return -EINVAL; }the boot logs would show: Flag 0x01000000, expected 0x00000001 The issue did not happen prior to 6f3189f38a3e ("bpf: treewide: Annotate BPF kfuncs in BTF") has only 0 was written before. It seems [1] will be addressing cross-compilation, but it did not fix it as is by just applying on top of master, so probably some of the changes will also need to be ported to `tools/include/linux/btf_ids.h`?
the fix in [1] is fixing flags in set8's pairs, but not the global flags it looks like Viktor's fix should now also swap that as well? like in the change below on top of Viktor's changes (untested) jirka ---
diff --git a/tools/bpf/resolve_btfids/main.c b/tools/bpf/resolve_btfids/main.c
index d01603ef6283..c44d57fec390 100644
--- a/tools/bpf/resolve_btfids/main.c
+++ b/tools/bpf/resolve_btfids/main.c@@ -706,6 +706,8 @@ static int sets_patch(struct object *obj) * correctly translate everything. */ if (need_bswap) { + set8->flags = bswap_32(set8->flags); + for (i = 0; i < cnt; i++) { set8->pairs[i].flags = bswap_32(set8->pairs[i].flags);