diff options
| author | Andrii Nakryiko <andrii@kernel.org> | 2021-05-07 08:41:15 +0300 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2021-05-12 01:07:17 +0300 |
| commit | 256eab48e70c0eaf5b1b9af83c0588491986c7de (patch) | |
| tree | 31f258d11a2de49f180040ebc7f74100c331993c /tools/testing/selftests/bpf/progs/tailcall_bpf2bpf2.c | |
| parent | fdbf5ddeb855a80831af2e5bb9db9218926e6789 (diff) | |
| download | linux-256eab48e70c0eaf5b1b9af83c0588491986c7de.tar.xz | |
selftests/bpf: Stop using static variables for passing data to/from user-space
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 <andrii@kernel.org>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Link: https://lore.kernel.org/bpf/20210507054119.270888-4-andrii@kernel.org
Diffstat (limited to 'tools/testing/selftests/bpf/progs/tailcall_bpf2bpf2.c')
| -rw-r--r-- | tools/testing/selftests/bpf/progs/tailcall_bpf2bpf2.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf2.c b/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf2.c index 7b1c04183824..3cc4c12817b5 100644 --- a/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf2.c +++ b/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf2.c @@ -20,7 +20,7 @@ int subprog_tail(struct __sk_buff *skb) return 1; } -static volatile int count; +int count = 0; SEC("classifier/0") int bpf_func_0(struct __sk_buff *skb) |