summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/bpf/progs/btf_dump_test_case_syntax.c
diff options
context:
space:
mode:
authorAndrii Nakryiko <andriin@fb.com>2020-03-02 16:32:32 -0800
committerDaniel Borkmann <daniel@iogearbox.net>2020-03-04 17:00:06 +0100
commit7cb30aaab3f277aa88e20a008faf57e0fb1119ec (patch)
tree6c4b74c76a30b236f29194e04c01d292f171e862 /tools/testing/selftests/bpf/progs/btf_dump_test_case_syntax.c
parent1aae4bdd787998ea331a56f3db9d8595790fe2f9 (diff)
downloadlinux-7cb30aaab3f277aa88e20a008faf57e0fb1119ec.tar.gz
linux-7cb30aaab3f277aa88e20a008faf57e0fb1119ec.tar.bz2
linux-7cb30aaab3f277aa88e20a008faf57e0fb1119ec.zip
libbpf: Assume unsigned values for BTF_KIND_ENUM
Currently, BTF_KIND_ENUM type doesn't record whether enum values should be interpreted as signed or unsigned. In Linux, most enums are unsigned, though, so interpreting them as unsigned matches real world better. Change btf_dump test case to test maximum 32-bit value, instead of negative value. Signed-off-by: Andrii Nakryiko <andriin@fb.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Link: https://lore.kernel.org/bpf/20200303003233.3496043-3-andriin@fb.com
Diffstat (limited to 'tools/testing/selftests/bpf/progs/btf_dump_test_case_syntax.c')
-rw-r--r--tools/testing/selftests/bpf/progs/btf_dump_test_case_syntax.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/testing/selftests/bpf/progs/btf_dump_test_case_syntax.c b/tools/testing/selftests/bpf/progs/btf_dump_test_case_syntax.c
index d4a02fe44a12..31975c96e2c9 100644
--- a/tools/testing/selftests/bpf/progs/btf_dump_test_case_syntax.c
+++ b/tools/testing/selftests/bpf/progs/btf_dump_test_case_syntax.c
@@ -13,7 +13,7 @@ enum e1 {
enum e2 {
C = 100,
- D = -100,
+ D = 4294967295,
E = 0,
};