Re: [PATCH bpf-next v1 06/14] bpf: Correct kfunc argument diagnostics

On Sun, 2026-08-16 at 03:57 +0200, Kumar Kartikeya Dwivedi wrote:
> The Call Type Safety diagnostics mishandle three kfunc argument classes.
> 
> BTF type ID 0 represents void, but btf_show_name() also uses zero to end
> type traversal. A pointer that resolves to void therefore loses its pointee
> name and is rendered as "()". End traversal directly for concrete terminal
> types, but resolve referenced types before testing for ID zero, and name the
> void terminal type explicitly. Format the complete parameter pointer type
> for nullable kfunc arguments, so void pointers are reported as (void *).
> 
> Also add the missing structured report when an __szk memory-size argument is
> not a verifier-known constant. Describe the generic bpf_refcount_acquire()
> contract without deriving an object type from its void pointer prototype.
> 
> Link: https://lore.kernel.org/bpf/[email protected]/
> Signed-off-by: Kumar Kartikeya Dwivedi <[email protected]>
> ---

Acked-by: Eduard Zingerman <[email protected]>

...