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 v5 00/14] Redesign Verification Errors
Date: Sat, 15 Aug 2026 18:57:16 +0000 [thread overview]
Message-ID: <178682023625.53386.10978136746024990805.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260815064612.378577-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:
On Sat, 15 Aug 2026 08:45:55 +0200 you wrote:
> TL;DR: This set reworks verifier error messages to include source and
> instruction annotations, together with more causal context, making
> failures easier to understand and more actionable when debugging and
> repairing BPF programs.
>
> Changelog:
>
> [...]
Here is the summary with links:
- [bpf-next,v5,01/14] bpf: Add verifier diagnostics report helpers
https://git.kernel.org/bpf/bpf-next/c/5ad746166341
- [bpf-next,v5,02/14] bpf: Add source and instruction diagnostic context
https://git.kernel.org/bpf/bpf-next/c/b9c5d822f677
- [bpf-next,v5,03/14] bpf: Add verifier diagnostic event log
https://git.kernel.org/bpf/bpf-next/c/daf8248701b6
- [bpf-next,v5,04/14] bpf: Prune verifier diagnostics when switching paths
https://git.kernel.org/bpf/bpf-next/c/a6debd5f25c9
- [bpf-next,v5,05/14] bpf: Track verifier register diagnostic events
(no matching commit)
- [bpf-next,v5,06/14] bpf: Track verifier reference diagnostic events
https://git.kernel.org/bpf/bpf-next/c/9ecd70304e28
- [bpf-next,v5,07/14] bpf: Track verifier context diagnostic events
(no matching commit)
- [bpf-next,v5,08/14] bpf: Report Register Type Safety errors
https://git.kernel.org/bpf/bpf-next/c/d63284e62b31
- [bpf-next,v5,09/14] bpf: Report Memory Safety bounds errors
(no matching commit)
- [bpf-next,v5,10/14] bpf: Report Resource Lifetime reference leaks
https://git.kernel.org/bpf/bpf-next/c/5d5764627555
- [bpf-next,v5,11/14] bpf: Report Call Type Safety argument errors
https://git.kernel.org/bpf/bpf-next/c/66e2727395dd
- [bpf-next,v5,12/14] bpf: Report Execution Context Safety errors
https://git.kernel.org/bpf/bpf-next/c/99a6a288a82b
- [bpf-next,v5,13/14] bpf: Report Program Structure CFG errors
https://git.kernel.org/bpf/bpf-next/c/a8f427835394
- [bpf-next,v5,14/14] bpf: Report Policy helper and kfunc errors
https://git.kernel.org/bpf/bpf-next/c/ac545b00ca56
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-15 18:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 6:45 [PATCH bpf-next v5 00/14] Redesign Verification Errors Kumar Kartikeya Dwivedi
2026-08-15 6:45 ` [PATCH bpf-next v5 01/14] bpf: Add verifier diagnostics report helpers Kumar Kartikeya Dwivedi
2026-08-15 6:52 ` sashiko-bot
2026-08-15 7:20 ` bot+bpf-ci
2026-08-15 6:45 ` [PATCH bpf-next v5 02/14] bpf: Add source and instruction diagnostic context Kumar Kartikeya Dwivedi
2026-08-15 7:01 ` sashiko-bot
2026-08-15 7:34 ` bot+bpf-ci
2026-08-15 6:45 ` [PATCH bpf-next v5 03/14] bpf: Add verifier diagnostic event log Kumar Kartikeya Dwivedi
2026-08-15 7:34 ` bot+bpf-ci
2026-08-15 6:45 ` [PATCH bpf-next v5 04/14] bpf: Prune verifier diagnostics when switching paths Kumar Kartikeya Dwivedi
2026-08-15 6:46 ` [PATCH bpf-next v5 05/14] bpf: Track verifier register diagnostic events Kumar Kartikeya Dwivedi
2026-08-15 7:34 ` bot+bpf-ci
2026-08-15 7:38 ` sashiko-bot
2026-08-15 6:46 ` [PATCH bpf-next v5 06/14] bpf: Track verifier reference " Kumar Kartikeya Dwivedi
2026-08-15 6:46 ` [PATCH bpf-next v5 07/14] bpf: Track verifier context " Kumar Kartikeya Dwivedi
2026-08-15 7:20 ` bot+bpf-ci
2026-08-15 6:46 ` [PATCH bpf-next v5 08/14] bpf: Report Register Type Safety errors Kumar Kartikeya Dwivedi
2026-08-15 7:34 ` bot+bpf-ci
2026-08-15 17:29 ` Eduard Zingerman
2026-08-15 6:46 ` [PATCH bpf-next v5 09/14] bpf: Report Memory Safety bounds errors Kumar Kartikeya Dwivedi
2026-08-15 6:59 ` sashiko-bot
2026-08-15 7:34 ` bot+bpf-ci
2026-08-15 6:46 ` [PATCH bpf-next v5 10/14] bpf: Report Resource Lifetime reference leaks Kumar Kartikeya Dwivedi
2026-08-15 7:34 ` bot+bpf-ci
2026-08-15 17:36 ` Eduard Zingerman
2026-08-15 6:46 ` [PATCH bpf-next v5 11/14] bpf: Report Call Type Safety argument errors Kumar Kartikeya Dwivedi
2026-08-15 7:49 ` bot+bpf-ci
2026-08-15 18:00 ` Eduard Zingerman
2026-08-15 6:46 ` [PATCH bpf-next v5 12/14] bpf: Report Execution Context Safety errors Kumar Kartikeya Dwivedi
2026-08-15 7:34 ` bot+bpf-ci
2026-08-15 6:46 ` [PATCH bpf-next v5 13/14] bpf: Report Program Structure CFG errors Kumar Kartikeya Dwivedi
2026-08-15 7:34 ` bot+bpf-ci
2026-08-15 17:50 ` Eduard Zingerman
2026-08-15 6:46 ` [PATCH bpf-next v5 14/14] bpf: Report Policy helper and kfunc errors Kumar Kartikeya Dwivedi
2026-08-15 7:20 ` bot+bpf-ci
2026-08-15 17:39 ` Eduard Zingerman
2026-08-15 18:57 ` 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=178682023625.53386.10978136746024990805.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