diff options
author | Andrii Nakryiko <andrii@kernel.org> | 2024-01-24 05:21:15 +0300 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2024-01-25 03:21:02 +0300 |
commit | aeaa97b006ddc7a8bf13e4adfdd02b3526f648a7 (patch) | |
tree | b3ccdcf15c0f24c2ba9ecaf3d3b1808984dfefaa /kernel/bpf/arraymap.c | |
parent | 0054493e5141b16e316b8c52d6aa534397e48b6c (diff) | |
download | linux-aeaa97b006ddc7a8bf13e4adfdd02b3526f648a7.tar.xz |
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.
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Christian Brauner <brauner@kernel.org>
Acked-by: John Fastabend <john.fastabend@gmail.com>
Link: https://lore.kernel.org/bpf/20240124022127.2379740-19-andrii@kernel.org
Diffstat (limited to 'kernel/bpf/arraymap.c')
0 files changed, 0 insertions, 0 deletions