Re: [PATCH bpf-next v9 0/3] bpf: arena: handle memory.max on fault-in with reclaim

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue, 22 Sep 2026 18:17:32 +0800 you wrote:
> Since commit e66fe1bc6d25 ("bpf: arena: Reintroduce memcg accounting"),
> arena pages are charged to the memcg of the process that created the arena.
> That exposes a problem in the arena user page fault path: the fault-in
> allocation runs under arena->spinlock, so it can only use the non-blocking
> allocator, which never reclaims. Once memory.current is at memory.max the
> allocation simply fails, even when the memcg is full of page cache that
> could be dropped right away. Reaching memory.max is completely normal for a
> healthy application - e.g. reading a large file fills memory.current with
> page cache - and the process then gets SIGSEGV on a perfectly valid arena
> address.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v9,1/3] bpf: arena: allocate the fault-in page outside the lock
    https://git.kernel.org/bpf/bpf-next/c/c7cd8be3d72f
  - [bpf-next,v9,2/3] selftests/bpf: Add read_cgroup_file() to cgroup_helpers
    https://git.kernel.org/bpf/bpf-next/c/a781db31b484
  - [bpf-next,v9,3/3] selftests/bpf: Add a test for arena fault-in under memory.max
    https://git.kernel.org/bpf/bpf-next/c/1fe5a5cd01e4

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