summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorSami Tolvanen <samitolvanen@google.com>2026-01-10 11:25:50 +0300
committerAlexei Starovoitov <ast@kernel.org>2026-01-13 05:53:57 +0300
commitb40a5d724f29fc2eed23ff353808a9aae616b48a (patch)
tree7e3ef0c3f9fcbd1a256a14e7dfa654682dd06be5 /include/linux
parent5714ca8cba5ed736f3733663c446cbee63a10a64 (diff)
downloadlinux-b40a5d724f29fc2eed23ff353808a9aae616b48a.tar.xz
bpf: crypto: Use the correct destructor kfunc type
With CONFIG_CFI enabled, the kernel strictly enforces that indirect function calls use a function pointer type that matches the target function. I ran into the following type mismatch when running BPF self-tests: CFI failure at bpf_obj_free_fields+0x190/0x238 (target: bpf_crypto_ctx_release+0x0/0x94; expected type: 0xa488ebfc) Internal error: Oops - CFI: 00000000f2008228 [#1] SMP ... As bpf_crypto_ctx_release() is also used in BPF programs and using a void pointer as the argument would make the verifier unhappy, add a simple stub function with the correct type and register it as the destructor kfunc instead. Signed-off-by: Sami Tolvanen <samitolvanen@google.com> Acked-by: Yonghong Song <yonghong.song@linux.dev> Tested-by: Viktor Malik <vmalik@redhat.com> Link: https://lore.kernel.org/r/20260110082548.113748-7-samitolvanen@google.com Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions