Re: [PATCH bpf-next v3 0/5] bpf, x86: enable EXECMEM_ROX_CACHE for BPF allocations

[patchwork-bot+netdevbpf]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@xxxxxxxxx>:

On Thu, 16 Jul 2026 10:51:34 +0300 you wrote:
> Hi,
> 
> BPF allocations of executable memory on x86 are essentially read-only. Most
> paths that call bpf_jit_alloc_exec() immediately make it ROX with
> set_memory_rox().
> 
> The code generation, at least on x86, uses separately allocated writable
> buffers and then updates the actual text memory with text_poke().
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/5] bpf: dispatcher: allocate bpf_dispatcher->rw_image with vzalloc()
    https://git.kernel.org/bpf/bpf-next/c/810a273919df
  - [bpf-next,v3,2/5] bpf: drop __weak from bpf_jit_alloc_exec() and bpf_jit_free_exec()
    https://git.kernel.org/bpf/bpf-next/c/4946eb5d37cb
  - [bpf-next,v3,3/5] bpf: alloc_prog_pack(): skip ROX management for already ROX memory
    https://git.kernel.org/bpf/bpf-next/c/7516714947da
  - [bpf-next,v3,4/5] bpf, x86: make sure allocation in arch_bpf_trampoline_size() is writable
    https://git.kernel.org/bpf/bpf-next/c/5bf02dbf39fa
  - [bpf-next,v3,5/5] x86/bpf: enable EXECMEM_ROX_CACHE for BPF allocations
    https://git.kernel.org/bpf/bpf-next/c/6b88aaec81db

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