From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v8 0/6] Improve stack depth verification stats output
Date: Thu, 13 Aug 2026 00:50:14 +0000 [thread overview]
Message-ID: <178658221464.2168272.5125774255091198511.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260812221925.3358041-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:
On Thu, 13 Aug 2026 00:19:17 +0200 you wrote:
> Some improvements for more clarity in the stack depth verification
> statistics output. See commit logs for details.
>
> For example, ./test_progs -t subprogs/subprogs_alone loads prog4,
> which has a main program, two static subprograms, and two independently
> verified global subprograms. A sample run produces:
>
> [...]
Here is the summary with links:
- [bpf-next,v8,1/6] bpf: Track verifier instruction stats for each subprogram
https://git.kernel.org/bpf/bpf-next/c/14c950ac2be8
- [bpf-next,v8,2/6] bpf: Attribute async callback instructions to verification roots
https://git.kernel.org/bpf/bpf-next/c/6137fb7c5f83
- [bpf-next,v8,3/6] bpf: Show more useful info in stack depth stats
https://git.kernel.org/bpf/bpf-next/c/c2e6c7de8830
- [bpf-next,v8,4/6] selftests/bpf: Adjust veristat stack depth parsing
https://git.kernel.org/bpf/bpf-next/c/502686233493
- [bpf-next,v8,5/6] selftests/bpf: Test stack depth stats without BTF subprog names
https://git.kernel.org/bpf/bpf-next/c/b961cf317100
- [bpf-next,v8,6/6] selftests/bpf: Test subprogram instruction statistics
https://git.kernel.org/bpf/bpf-next/c/5cb481e1391a
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-08-13 0:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 22:19 [PATCH bpf-next v8 0/6] Improve stack depth verification stats output Kumar Kartikeya Dwivedi
2026-08-12 22:19 ` [PATCH bpf-next v8 1/6] bpf: Track verifier instruction stats for each subprogram Kumar Kartikeya Dwivedi
2026-08-12 22:19 ` [PATCH bpf-next v8 2/6] bpf: Attribute async callback instructions to verification roots Kumar Kartikeya Dwivedi
2026-08-13 0:39 ` Eduard Zingerman
2026-08-12 22:19 ` [PATCH bpf-next v8 3/6] bpf: Show more useful info in stack depth stats Kumar Kartikeya Dwivedi
2026-08-12 22:29 ` sashiko-bot
2026-08-12 23:14 ` bot+bpf-ci
2026-08-12 22:19 ` [PATCH bpf-next v8 4/6] selftests/bpf: Adjust veristat stack depth parsing Kumar Kartikeya Dwivedi
2026-08-12 23:14 ` bot+bpf-ci
2026-08-12 22:19 ` [PATCH bpf-next v8 5/6] selftests/bpf: Test stack depth stats without BTF subprog names Kumar Kartikeya Dwivedi
2026-08-12 23:14 ` bot+bpf-ci
2026-08-12 22:19 ` [PATCH bpf-next v8 6/6] selftests/bpf: Test subprogram instruction statistics Kumar Kartikeya Dwivedi
2026-08-13 0:50 ` 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=178658221464.2168272.5125774255091198511.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=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox