From: patchwork-bot+netdevbpf@kernel.org
To: Paul Chaignon <paul.chaignon@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next v3 0/3] bpf: Maximum combined stack depth
Date: Thu, 14 May 2026 01:40:09 +0000 [thread overview]
Message-ID: <177872280980.3914219.4817879194920517908.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1778700777.git.paul.chaignon@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 13 May 2026 21:33:41 +0200 you wrote:
> This patchset dumps the maximum combined stack depth in verifier logs
> and parses it in veristat.
>
> Changes in v3:
> - Increment spec_cnt field in veristat for new MAX_STACK id (AI bot).
> Changes in v2:
> - Remove unnecessary max_stack_depth assignment (Eduard).
> - Fix and test incorrect handling of private stacks.
> - Add veristat metric (Eduard).
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/3] bpf: Report maximum combined stack depth
https://git.kernel.org/bpf/bpf-next/c/f41f34ec6474
- [bpf-next,v3,2/3] selftests/bpf: Test reported max stack depth
https://git.kernel.org/bpf/bpf-next/c/2a5b22e87ba5
- [bpf-next,v3,3/3] veristat: Report max stack depth
https://git.kernel.org/bpf/bpf-next/c/f0015ffbf40c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-14 1:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 19:33 [PATCH bpf-next v3 0/3] bpf: Maximum combined stack depth Paul Chaignon
2026-05-13 19:34 ` [PATCH bpf-next v3 1/3] bpf: Report maximum " Paul Chaignon
2026-05-13 23:24 ` Eduard Zingerman
2026-05-13 19:35 ` [PATCH bpf-next v3 2/3] selftests/bpf: Test reported max " Paul Chaignon
2026-05-13 23:31 ` Eduard Zingerman
2026-05-13 19:35 ` [PATCH bpf-next v3 3/3] veristat: Report " Paul Chaignon
2026-05-13 23:23 ` Eduard Zingerman
2026-05-14 1:40 ` 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=177872280980.3914219.4817879194920517908.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.com \
--cc=paul.chaignon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox