Re: [PATCH bpf v3 0/2] bpf, x86: fix per-CPU address resolution into an extended register

Hello:

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

On Fri, 14 Aug 2026 15:02:52 -0700 you wrote:
> The JIT resolves a per-CPU address with
> 
>   add <dst>, gs:[this_cpu_off]
> 
> but builds the REX prefix with add_1mod(), which sets REX.B. The
> destination is encoded in ModRM.reg, which REX.R extends, and the memory
> operand is disp32 with no base, so REX.B does nothing and the high
> register bit is dropped. Every extended destination therefore resolves
> into whichever register shares the low three bits:
> 
> [...]

Here is the summary with links:
  - [bpf,v3,1/2] bpf, x86: Fix per-CPU address resolution into an extended register
    https://git.kernel.org/bpf/bpf-next/c/5bbbce02e500
  - [bpf,v3,2/2] selftests/bpf: Check per-CPU address resolution per register
    https://git.kernel.org/bpf/bpf-next/c/f61306e8c98c

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