Re: [PATCH bpf-next v5 0/3] bpf: Fix trampoline handling of 128-bit values

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <[email protected]>:

On Tue, 28 Jul 2026 22:01:54 -0700 you wrote:
> The BPF trampoline preserves only 8 bytes of a target function's return
> value (R0), and its register save area under-allocates space for 128-bit
> arguments for x86_64. These two problems lead to memory corruption or
> incorrect values observed by BPF programs and the real caller.
> 
> This series fixes both issues and adds two selftests, otherwise, each of
> them will fail if without the corresponding fix.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/3] bpf: Reject >8 byte return values on return-reading trampoline paths
    https://git.kernel.org/bpf/bpf-next/c/c48796aa6c39
  - [bpf-next,v5,2/3] bpf, x86: Fix trampoline stack size for 128-bit arguments
    https://git.kernel.org/bpf/bpf-next/c/814cba835ef6
  - [bpf-next,v5,3/3] selftests/bpf: Add tests for >8 byte return value and 128-bit arguments
    https://git.kernel.org/bpf/bpf-next/c/13cc6b788b1a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html