Re: [PATCH bpf-next v2 0/2] bpf: Fix loop detection for re-arming async callbacks

[patchwork-bot+netdevbpf@kernel.org]

Hello:

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

On Thu, 24 Sep 2026 09:26:05 -0700 you wrote:
> Changelog:
> v1: https://lore.kernel.org/all/20260923140152.4005097-1-puranjay@kernel.org/
> Changes in v2:
> - Patch 1: also fix push_callback_call(), which numbered a new entry
>   from the caller frame. When the callback re-arms from a subprog that
>   frame is not frame 0 and its count is 0, so every entry was numbered 1,
>   is_state_visited() never saw a difference, and a loop in such a
>   callback was still rejected.
> - Patch 2: loop_cb() now re-arms through a __noinline subprog, so the
>   caller frame at bpf_timer_set_callback() is not the callback's own
>   frame. The v1 test re-armed from frame 0 and passed without the
>   push_callback_call() fix.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: Look at frame 0 when telling async callback entries apart
    https://git.kernel.org/bpf/bpf-next/c/e55220162aae
  - [bpf-next,v2,2/2] selftests/bpf: Add timer tests for a re-arming callback with a loop
    https://git.kernel.org/bpf/bpf-next/c/84bff37db2ad

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