From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, npc@anthropic.com
Subject: Re: [PATCH bpf 1/2] bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks
Date: Wed, 02 Sep 2026 18:20:07 +0000 [thread overview]
Message-ID: <178837320765.2884595.7267988121668407897.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831-bug-015-backtrack-cb-args-precise-v1-1-68a8e2a821e0@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 31 Aug 2026 18:36:09 -0700 you wrote:
> When processing calls to bpf_loop() verifier marks R1 (and R4) as
> precise. R1 tracks loop iterations number and because of the
> 'callback_depth < R1' mechanics in check_helper_call() must be marked
> precise. However, precision propagation for R1 was broken,
> when bpf_loop() call was verified on a second iteration.
>
> Consider the following verification trace:
> - main: bpf_loop(nr_loops, callback ...)
> - callback: BPF_EXIT
> - main: bpf_loop(nr_loops, callback ...)
> - ...
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks
https://git.kernel.org/bpf/bpf/c/e3e4f66cc4b7
- [bpf,2/2] selftests/bpf: test case for unsafe pruning of bpf_loop checkpoints
https://git.kernel.org/bpf/bpf/c/7ac966218906
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-09-02 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 1:36 [PATCH bpf 1/2] bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks Eduard Zingerman
2026-09-01 1:36 ` [PATCH bpf 2/2] selftests/bpf: test case for unsafe pruning of bpf_loop checkpoints Eduard Zingerman
2026-09-01 2:02 ` [PATCH bpf 1/2] bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks sashiko-bot
2026-09-01 6:20 ` Eduard Zingerman
2026-09-02 18: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=178837320765.2884595.7267988121668407897.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=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=npc@anthropic.com \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.