diff options
author | David Vernet <void@manifault.com> | 2023-08-14 21:59:07 +0300 |
---|---|---|
committer | Martin KaFai Lau <martin.lau@kernel.org> | 2023-08-15 08:23:39 +0300 |
commit | 8ba651ed7fa1641f7c4941b79f2e3dd4ddb58aec (patch) | |
tree | e30a1e5f2b94d7c3a22a97988051e7bfdd420b7e /include | |
parent | ccd9a8be2e42a337ad4da5d8a051e8293200a4f3 (diff) | |
download | linux-8ba651ed7fa1641f7c4941b79f2e3dd4ddb58aec.tar.xz |
bpf: Support default .validate() and .update() behavior for struct_ops links
Currently, if a struct_ops map is loaded with BPF_F_LINK, it must also
define the .validate() and .update() callbacks in its corresponding
struct bpf_struct_ops in the kernel. Enabling struct_ops link is useful
in its own right to ensure that the map is unloaded if an application
crashes. For example, with sched_ext, we want to automatically unload
the host-wide scheduler if the application crashes. We would likely
never support updating elements of a sched_ext struct_ops map, so we'd
have to implement these callbacks showing that they _can't_ support
element updates just to benefit from the basic lifetime management of
struct_ops links.
Let's enable struct_ops maps to work with BPF_F_LINK even if they
haven't defined these callbacks, by assuming that a struct_ops map
element cannot be updated by default.
Acked-by: Kui-Feng Lee <thinker.li@gmail.com>
Signed-off-by: David Vernet <void@manifault.com>
Link: https://lore.kernel.org/r/20230814185908.700553-2-void@manifault.com
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions