aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/bpf/progs/test_probe_user.c
diff options
context:
space:
mode:
authorAndrii Nakryiko <andriin@fb.com>2020-01-10 10:19:16 -0800
committerAlexei Starovoitov <ast@kernel.org>2020-01-10 10:38:00 -0800
commit1d1a3bcffe360a56fd8cc287ed74d4c3066daf42 (patch)
treea5dd199f093ed5cd8a2dd179c2682ea5520b26b5 /tools/testing/selftests/bpf/progs/test_probe_user.c
parentMerge branch 'bpf-global-funcs' (diff)
downloadlinux-dev-1d1a3bcffe360a56fd8cc287ed74d4c3066daf42.tar.xz
linux-dev-1d1a3bcffe360a56fd8cc287ed74d4c3066daf42.zip
libbpf: Poison kernel-only integer types
It's been a recurring issue with types like u32 slipping into libbpf source code accidentally. This is not detected during builds inside kernel source tree, but becomes a compilation error in libbpf's Github repo. Libbpf is supposed to use only __{s,u}{8,16,32,64} typedefs, so poison {s,u}{8,16,32,64} explicitly in every .c file. Doing that in a bit more centralized way, e.g., inside libbpf_internal.h breaks selftests, which are both using kernel u32 and libbpf_internal.h. This patch also fixes a new u32 occurence in libbpf.c, added recently. Fixes: 590a00888250 ("bpf: libbpf: Add STRUCT_OPS support") Signed-off-by: Andrii Nakryiko <andriin@fb.com> Signed-off-by: Alexei Starovoitov <ast@kernel.org> Acked-by: Martin KaFai Lau <kafai@fb.com> Link: https://lore.kernel.org/bpf/20200110181916.271446-1-andriin@fb.com
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions