diff options
author | Stanislav Fomichev <sdf@google.com> | 2022-04-14 18:12:33 +0200 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2022-04-19 18:45:47 +0200 |
commit | 055eb95533273bc334794dbc598400d10800528f (patch) | |
tree | 7b694e74401831a39e0c5e3b6bd0c8416a77cc7f /init/calibrate.c | |
parent | selftests/bpf: Refactor prog_tests logging and test execution (diff) | |
download | linux-055eb95533273bc334794dbc598400d10800528f.tar.xz linux-055eb95533273bc334794dbc598400d10800528f.zip |
bpf: Move rcu lock management out of BPF_PROG_RUN routines
Commit 7d08c2c91171 ("bpf: Refactor BPF_PROG_RUN_ARRAY family of macros
into functions") switched a bunch of BPF_PROG_RUN macros to inline
routines. This changed the semantic a bit. Due to arguments expansion
of macros, it used to be:
rcu_read_lock();
array = rcu_dereference(cgrp->bpf.effective[atype]);
...
Now, with with inline routines, we have:
array_rcu = rcu_dereference(cgrp->bpf.effective[atype]);
/* array_rcu can be kfree'd here */
rcu_read_lock();
array = rcu_dereference(array_rcu);
I'm assuming in practice rcu subsystem isn't fast enough to trigger
this but let's use rcu API properly.
Also, rename to lower caps to not confuse with macros. Additionally,
drop and expand BPF_PROG_CGROUP_INET_EGRESS_RUN_ARRAY.
See [1] for more context.
[1] https://lore.kernel.org/bpf/CAKH8qBs60fOinFdxiiQikK_q0EcVxGvNTQoWvHLEUGbgcj1UYg@mail.gmail.com/T/#u
v2
- keep rcu locks inside by passing cgroup_bpf
Fixes: 7d08c2c91171 ("bpf: Refactor BPF_PROG_RUN_ARRAY family of macros into functions")
Signed-off-by: Stanislav Fomichev <sdf@google.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Martin KaFai Lau <kafai@fb.com>
Link: https://lore.kernel.org/bpf/20220414161233.170780-1-sdf@google.com
Diffstat (limited to 'init/calibrate.c')
0 files changed, 0 insertions, 0 deletions