diff options
author | 2023-12-13 11:08:33 -0800 | |
---|---|---|
committer | 2023-12-13 15:47:04 -0800 | |
commit | f5fdb51fb980077a4c6c78f3f775821f611fb38b (patch) | |
tree | fa1e7a72820564b8bab55f1c448f446d68b0c41f /tools/lib/bpf/libbpf_internal.h | |
parent | bpf: selftests: Add verifier tests for CO-RE bitfield writes (diff) | |
download | wireguard-linux-f5fdb51fb980077a4c6c78f3f775821f611fb38b.tar.xz wireguard-linux-f5fdb51fb980077a4c6c78f3f775821f611fb38b.zip |
bpf: fail BPF_TOKEN_CREATE if no delegation option was set on BPF FS
It's quite confusing in practice when it's possible to successfully
create a BPF token from BPF FS that didn't have any of delegate_xxx
mount options set up. While it's not wrong, it's actually more
meaningful to reject BPF_TOKEN_CREATE with specific error code (-ENOENT)
to let user-space know that no token delegation is setup up.
So, instead of creating empty BPF token that will be always ignored
because it doesn't have any of the allow_xxx bits set, reject it with
-ENOENT. If we ever need empty BPF token to be possible, we can support
that with extra flag passed into BPF_TOKEN_CREATE.
Acked-by: Christian Brauner <brauner@kernel.org>
Acked-by: John Fastabend <john.fastabend@gmail.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/r/20231213190842.3844987-2-andrii@kernel.org
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/lib/bpf/libbpf_internal.h')
0 files changed, 0 insertions, 0 deletions