libbpf: add bpf object kern_version attribute setter
PATCH v2 1/1 libbpf: add bpf object kern_version attribute setter
Unfortunately some distros don't have their kernel version defined accurately in <linux/version.h> due to different long term support reasons.
It is important to have a way to override the bpf kern_version attribute during runtime: some old kernels might still check for kern_version attribute during bpf_prog_load().
--- src/libbpf.c | 10 ++++++++++ src/libbpf.h | 1 + 2 files changed, 11 insertions(+)
src/libbpf.c +10 -0
@@ -8278,6 +8278,16 @@ int bpf_object__btf_fd(const struct bpf_object *obj)return obj->btf ?btf__fd (obj->btf) :-1 ; } +int bpf_object__set_kversion (struct bpf_object *obj,__u32 kern_version) +{ +if (obj->loaded) +return -1 ; + + obj->kern_version = kern_version; + +return 0 ; +} +int bpf_object__set_priv (struct bpf_object *obj,void *priv,bpf_object_clear_priv_t clear_priv) {
src/libbpf.h +1 -0
@@ -143,6 +143,7 @@ LIBBPF_API int bpf_object__unload(struct bpf_object *obj); LIBBPF_API const char *bpf_object__name(const struct bpf_object *obj); LIBBPF_API unsigned int bpf_object__kversion(const struct bpf_object *obj); +LIBBPF_API int bpf_object__set_kversion(struct bpf_object *obj, __u32 kern_version);struct btf ; LIBBPF_API struct btf *bpf_object__btf(const struct bpf_object *obj);
Signature · 1 line
2.27.0
Quoted 11 lines · Rafael David Tinoco
Unfortunately some distros don't have their kernel version defined accurately in <
linux/version.h> due to different long term support reasons.It is important to have a way to override the bpf
kern_versionattribute during runtime: some old kernels might still check forkern_versionattribute duringbpf_prog_load().Signed-off-by Rafael David Tinoco <[email protected]>---
Ok, getting close, but probably another iteration is needed.
Quoted 9 lines
src/libbpf.c | 10 ++++++++++ src/libbpf.h | 1 + 2 files changed, 11 insertions(+)src/libbpf.c +0
-0
src/libbpf.c int bpf_object__btf_fd(const struct bpf_object *obj) · line 8284
Quoted 7 lines
src/libbpf.c +4
-0@@ -8278,6 +8278,16 @@ int bpf_object__btf_fd(const struct bpf_object *obj)return obj->btf ?btf__fd (obj->btf) :-1 ; } +int bpf_object__set_kversion (struct bpf_object *obj,__u32 kern_version) +{ +if (obj->loaded) +return -1 ;
other functions return -EINVAL in such cases. -1 is actually -EPERM, which is very misleading, please update
Quoted 14 lines
src/libbpf.c +6
-0+ + obj->kern_version = kern_version; + +return 0 ; +} +int bpf_object__set_priv (struct bpf_object *obj,void *priv,bpf_object_clear_priv_t clear_priv) {src/libbpf.h +0
-0
src/libbpf.h LIBBPF_API int bpf_object__unload(struct bpf_object *obj); · line 146
Quoted 4 lines
src/libbpf.h +1
-0@@ -143,6 +143,7 @@ LIBBPF_API int bpf_object__unload(struct bpf_object *obj); LIBBPF_API const char *bpf_object__name(const struct bpf_object *obj); LIBBPF_API unsigned int bpf_object__kversion(const struct bpf_object *obj); +LIBBPF_API int bpf_object__set_kversion(struct bpf_object *obj, __u32 kern_version);
have you run libbpf's Makefile? It should have complained about bpf_object__set_kversion symbol mismatches/etc. That means that this API needs to be listed in libbpf.map file, please add it there (to latest version, 0.4, and also preserve alphabetical order). Thanks.
Quoted 6 lines
src/libbpf.h +0
-1struct btf ; LIBBPF_API struct btf *bpf_object__btf(const struct bpf_object *obj); --2.27.0
Quoted 8 lines
Quoted 3 lines
+LIBBPF_API int
bpf_object__set_kversion(struct bpf_object *obj, __u32 kern_version);have you run libbpf's
Makefile? It should have complained aboutbpf_object__set_kversionsymbol mismatches/etc. That means that this API needs to be listed in libbpf.map file, please add it there (to latest version, 0.4, and also preserve alphabetical order). Thanks.
Alright, sending a v3 with changes. I had only static builds on my side and it didn’t run assigned linker version-script. Will include in my tests before further submissions.
Quoted 5 lines · Rafael David Tinoco
Quoted 5 lines
Quoted 4 lines
+LIBBPF_API int
bpf_object__set_kversion(struct bpf_object *obj, __u32 kern_version);
Quoted 10 lines
Quoted 4 lines
have you run libbpf's
Makefile? It should have complained aboutbpf_object__set_kversionsymbol mismatches/etc. That means that this API needs to be listed in libbpf.map file, please add it there (to latest version, 0.4, and also preserve alphabetical order). Thanks.Alright, sending a v3 with changes. I had only static builds on my side and it didn’t run assigned linker version-script. Will include in my tests before further submissions.
Oh, I just noticed that you based your patch on top of Github repository. libbpf sources actually live and are developed against bpf-next kernel tree. Github repository is periodically synced from kernel trees with a special script. Please do the development against libbpf sources in the kernel tree (in tools/lib/bpf). You should also try running selftests from tools/testing/selftests/bpf, especially sudo ./test_progs. You'll need very recent Clang built from sources to build and run everything. But at least you won't have to spend efforts setting up your VM for testing, see vmtest.sh script in selftests, added recently by KP Singh. It will build latest kernel and will spin up qemu VM to run tests.
It's a bit of an upfront setup, but if you are intending to keep contributing to libbpf and kernel, it's worth it :)
Also we have CI that would automatically test submitted patch sets (see [0]). See also [1] for the build for your v2.
[0] https://github.com/kernel-patches/bpf/pulls
[1] https://travis-ci.com/github/kernel-patches/bpf/builds/220716720