selftests/bpf: Stop using static variables for passing data to/from user-space

2021-05-11T22:07:17Z

In preparation of skipping emitting static variables in BPF skeletons, switch all current selftests uses of static variables to pass data between BPF and user-space to use global variables. All non-read-only `static volatile` variables become just plain global variables by dropping `static volatile` part. Read-only `static volatile const` variables, though, still require `volatile` modifier, otherwise compiler will ignore whatever values are set from user-space. Few static linker tests are using name-conflicting static variables to validate that static linker still properly handles static variables and doesn't trip up on name conflicts. Signed-off-by: Andrii Nakryiko Signed-off-by: Alexei Starovoitov Link: https://lore.kernel.org/bpf/20210507054119.270888-4-andrii@kernel.org

selftests/bpf: Add a series of tests for bpf_snprintf

2021-04-19T22:27:37Z

The "positive" part tests all format specifiers when things go well. The "negative" part makes sure that incorrect format strings fail at load time. Signed-off-by: Florent Revest Signed-off-by: Alexei Starovoitov Link: https://lore.kernel.org/bpf/20210419155243.1632274-7-revest@chromium.org

kernel/tools/testing/selftests/bpf/progs/test_snprintf_single.c, branch linux-6.2.y

selftests/bpf: Stop using static variables for passing data to/from user-space

selftests/bpf: Add a series of tests for bpf_snprintf