Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <[email protected]>:
On Wed, 07 Oct 2026 16:25:28 +0000 you wrote:
> A global subprogram parameter tagged __arg_trusted is verified with
> PTR_TRUSTED, but its call-site type check also accepts bare PTR_TO_BTF_ID and
> MEM_RCU registers. This lets a callee use a pointer with weaker provenance
> under the trusted-pointer contract, including passing it to a non-KF_RCU
> kfunc.
>
> Encode the trusted-pointer requirement in generated kfunc prototypes and
> drive the shared provenance check from the argument contract. A KF_RCU
> kfunc additionally permits MEM_RCU, while a global __arg_trusted argument
> requires a referenced or trusted pointer. Normalize nullability when the
> argument contract permits it.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/2] bpf: Enforce trusted BTF ID argument provenance
https://git.kernel.org/bpf/bpf-next/c/c3a0bfddaee4
- [bpf-next,v4,2/2] selftests/bpf: Cover trusted BTF ID argument provenance
https://git.kernel.org/bpf/bpf-next/c/71b6a960c73f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
