Thread (13 messages) read the whole thread 13 messages, 4 authors, 2025-11-26

Re: [PATCH bpf-next v3 1/4] bpf: crypto: Use the correct destructor kfunc type

From: Yonghong Song <yonghong.song@linux.dev>
Date: 2025-07-28 23:08:09
Also in: bpf, lkml


On 7/28/25 1:26 PM, Sami Tolvanen wrote:
With CONFIG_CFI_CLANG 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>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help