All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next 0/9] bpf: Check chains of calls over the call graph, allow 32 frames
Date: Thu, 05 Nov 2026 01:30:10 +0000	[thread overview]
Message-ID: <179384221058.3342012.10154868315037998297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104215523.1852636-1-alexei.starovoitov@gmail.com>

Hello:

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

On Wed,  4 Nov 2026 21:55:14 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
> 
> check_max_stack_depth() walks the chains of calls of a prog one by one:
> 
>       main          main -> A -> C -> D
>       /  \          main -> A -> C -> E
>      A    B         main -> B -> C -> D
>       \  /          main -> B -> C -> E
>        C
>       / \
>      D   E
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/9] bpf: Build the call graph of a prog after the main verification pass
    https://git.kernel.org/bpf/bpf-next/c/e4b57476a300
  - [bpf-next,2/9] bpf: Use the call graph to find what runs in a callback
    https://git.kernel.org/bpf/bpf-next/c/904f23207eb1
  - [bpf-next,3/9] bpf: Use the call graph to find what gets to a tail call
    https://git.kernel.org/bpf/bpf-next/c/e7e2abda5f28
  - [bpf-next,4/9] bpf: Use the call graph to find callbacks that take a stack in arena
    https://git.kernel.org/bpf/bpf-next/c/4bf031da4fdb
  - [bpf-next,5/9] bpf: Use the call graph to choose subprogs with a private stack
    https://git.kernel.org/bpf/bpf-next/c/cfede35c4193
  - [bpf-next,6/9] bpf: Use the call graph to compute the depth of chains of calls
    https://git.kernel.org/bpf/bpf-next/c/abbf6b7c6626
  - [bpf-next,7/9] selftests/bpf: Test what follows from the chains of calls
    https://git.kernel.org/bpf/bpf-next/c/b6e223c6435e
  - [bpf-next,8/9] bpf: Bump MAX_CALL_FRAMES to 32
    https://git.kernel.org/bpf/bpf-next/c/1b00d7dcaa03
  - [bpf-next,9/9] selftests/bpf: Test 32 call frames
    https://git.kernel.org/bpf/bpf-next/c/32a1783fd695

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



      parent reply	other threads:[~2026-11-05  1:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 21:55 [PATCH bpf-next 0/9] bpf: Check chains of calls over the call graph, allow 32 frames Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 1/9] bpf: Build the call graph of a prog after the main verification pass Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 2/9] bpf: Use the call graph to find what runs in a callback Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 3/9] bpf: Use the call graph to find what gets to a tail call Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 4/9] bpf: Use the call graph to find callbacks that take a stack in arena Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 5/9] bpf: Use the call graph to choose subprogs with a private stack Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 6/9] bpf: Use the call graph to compute the depth of chains of calls Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 7/9] selftests/bpf: Test what follows from the " Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 8/9] bpf: Bump MAX_CALL_FRAMES to 32 Alexei Starovoitov
2026-11-04 22:40   ` bot+bpf-ci
2026-11-05  0:32     ` Alexei Starovoitov
2026-11-04 21:55 ` [PATCH bpf-next 9/9] selftests/bpf: Test 32 call frames Alexei Starovoitov
2026-11-05  1:30 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=179384221058.3342012.10154868315037998297.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=memxor@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.