From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next 0/2] bpf: One basic block and the way to it in the level 1 log
Date: Sun, 08 Nov 2026 16:20:05 +0000 [thread overview]
Message-ID: <179415480542.1631906.10076400287489305984.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261108053937.4134138-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 8 Nov 2026 05:39:35 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> At log level 1 the verifier prints each insn when it verifies it. It used
> to follow one path at a time. push_stack() noted the end of the log when
> it put a branch aside, and pop_stack() moved the log back there when it
> took the branch. So the log was the path from the first insn to the
> current one: never larger than the longest path, and for a rejected prog
> the path to the error.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Take the end of the verifier log out and append it later
https://git.kernel.org/bpf/bpf-next/c/ffb7ea52c7af
- [bpf-next,2/2] bpf: Keep one basic block in the level 1 log and print the way to it
https://git.kernel.org/bpf/bpf-next/c/35fca41d5746
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-11-08 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 5:39 [PATCH bpf-next 0/2] bpf: One basic block and the way to it in the level 1 log Alexei Starovoitov
2026-11-08 5:39 ` [PATCH bpf-next 1/2] bpf: Take the end of the verifier log out and append it later Alexei Starovoitov
2026-11-08 6:03 ` sashiko-bot
2026-11-08 16:08 ` Alexei Starovoitov
2026-11-08 5:39 ` [PATCH bpf-next 2/2] bpf: Keep one basic block in the level 1 log and print the way to it Alexei Starovoitov
2026-11-08 6:02 ` sashiko-bot
2026-11-08 16:08 ` Alexei Starovoitov
2026-11-08 16:20 ` 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=179415480542.1631906.10076400287489305984.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.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