From: Eduard Zingerman <eddyz87@gmail.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Emil Tsalapatis <emil@etsalapatis.com>,
kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v7 4/6] selftests/bpf: Adjust veristat stack depth parsing
Date: Tue, 11 Aug 2026 13:50:37 -0700 [thread overview]
Message-ID: <0c899eaef2ffeb53c37c75207775e8fce8cd6f47.camel@gmail.com> (raw)
In-Reply-To: <20260808062601.1070988-5-memxor@gmail.com>
On Sat, 2026-08-08 at 08:25 +0200, Kumar Kartikeya Dwivedi wrote:
> The verifier now reports instruction and stack depth statistics using
> uniform "subprog <id> (<name>) <kind>" records. Subprogram 0 is classified
> as main, while other records are global or static. Each record carries
> insns_self, insns_total, and stack depth.
>
> Teach veristat to parse the new records while retaining support for the
> legacy one-line stack depth format used by older kernels. Skip both
> instruction counts and match only through the stack value so fields can
> still be appended without breaking parsing.
>
> Increase the bounded backward scan so it can include all 256 per-subprogram
> records.
>
> Zero-initialize the legacy stack buffer because logs using the new format do
> not populate it before the trailing tokenizer loop. This makes the loop see
> an empty string instead of reading uninitialized data.
>
> Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
> @@ -1025,11 +1027,17 @@ static int parse_verif_log(char * const buf, size_t buf_sz, struct verif_stats *
> &s->stats[MARK_READ_MAX_LEN]))
> continue;
>
> + if (sscanf(cur, "stack depth max %ld", &s->stats[MAX_STACK]) == 1)
> + continue;
> + if (sscanf(cur, "subprog %*d %*s %*s insns_self %*d insns_total %*d stack %ld", &sub_stack) == 1) {
> + s->stats[STACK] += sub_stack;
> + continue;
> + }
Nit: a comment about why two different formats are matched would be helpful.
> if (2 == sscanf(cur, "stack depth %511s max %ld", stack, &s->stats[MAX_STACK]))
> continue;
> }
> while ((token = strtok_r(cnt++ ? NULL : stack, "+", &state))) {
> - if (sscanf(token, "%d", &sub_stack) == 0)
> + if (sscanf(token, "%ld", &sub_stack) == 0)
> break;
> s->stats[STACK] += sub_stack;
> }
next prev parent reply other threads:[~2026-08-11 20:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 6:25 [PATCH bpf-next v7 0/6] Improve stack depth verification stats output Kumar Kartikeya Dwivedi
2026-08-08 6:25 ` [PATCH bpf-next v7 1/6] bpf: Track verifier instruction stats for each subprogram Kumar Kartikeya Dwivedi
2026-08-11 19:35 ` Eduard Zingerman
2026-08-08 6:25 ` [PATCH bpf-next v7 2/6] bpf: Attribute async callback instructions to verification roots Kumar Kartikeya Dwivedi
2026-08-08 7:40 ` bot+bpf-ci
2026-08-11 20:01 ` Eduard Zingerman
2026-08-08 6:25 ` [PATCH bpf-next v7 3/6] bpf: Show more useful info in stack depth stats Kumar Kartikeya Dwivedi
2026-08-08 6:45 ` sashiko-bot
2026-08-11 20:04 ` Eduard Zingerman
2026-08-08 6:25 ` [PATCH bpf-next v7 4/6] selftests/bpf: Adjust veristat stack depth parsing Kumar Kartikeya Dwivedi
2026-08-11 20:50 ` Eduard Zingerman [this message]
2026-08-08 6:25 ` [PATCH bpf-next v7 5/6] selftests/bpf: Test stack depth stats without BTF subprog names Kumar Kartikeya Dwivedi
2026-08-11 21:18 ` Eduard Zingerman
2026-08-08 6:25 ` [PATCH bpf-next v7 6/6] selftests/bpf: Test subprogram instruction statistics Kumar Kartikeya Dwivedi
2026-08-08 6:36 ` sashiko-bot
2026-08-11 21:37 ` Eduard Zingerman
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=0c899eaef2ffeb53c37c75207775e8fce8cd6f47.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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