Re: [PATCH bpf-next v4 16/16] bpf: Gate verifier diagnostics on log level

Eduard Zingerman <[email protected]>
Newsgroups org.kernel.vger.bpf
Message-ID <[email protected]>
On Thu, 2026-08-13 at 01:33 +0200, Kumar Kartikeya Dwivedi wrote:
> Verifier diagnostics collect active-path history and render richer reports for
> selected verifier failures. That work is useful only when the caller requests
> normal verifier log output.
> 
> Do not enable diagnostic collection or report rendering for BPF_LOG_STATS-only
> loads. Stats-only loads still need the verifier's summary counters, but not
> the extra path history used by diagnostic reports.
> 
> Keep enablement in the verifier environment and requested log mode so async
> callback verification uses the same diagnostic policy as the main verifier
> pass.
> 
> Signed-off-by: Kumar Kartikeya Dwivedi <[email protected]>
> ---

Oh, I see why you needed the "current call chain".
Nope, let's keep the report useful on any log level, please figure out how.
The "current call chain" is completely useless.
Also, this whole business with check_max_stack_depth_subprog()
modification and limits reporting can be a follow-up.

...
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.