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,
npc@anthropic.com, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf v4 0/2] Compare stack frames in exact register states
Date: Sat, 19 Sep 2026 05:30:07 +0000 [thread overview]
Message-ID: <178979580765.1275551.2384650495430969417.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260919014213.1840880-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 19 Sep 2026 03:42:09 +0200 you wrote:
> regs_exact() compares register values and their ID relationships, but it
> does not compare frameno. regsafe() checks frameno for ordinary
> PTR_TO_STACK comparisons, while its EXACT path returns through regs_exact()
> before reaching that check. Infinite-loop detection can therefore mistake
> pointers to the same offset in different stack frames for the same pointer
> and reject a finite loop.
>
> [...]
Here is the summary with links:
- [bpf,v4,1/2] bpf: Compare stack frames in regs_exact()
https://git.kernel.org/bpf/bpf/c/8901cee9316d
- [bpf,v4,2/2] selftests/bpf: Cover frame changes in bounded loops
https://git.kernel.org/bpf/bpf/c/070587848985
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-19 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 1:42 [PATCH bpf v4 0/2] Compare stack frames in exact register states Kumar Kartikeya Dwivedi
2026-09-19 1:42 ` [PATCH bpf v4 1/2] bpf: Compare stack frames in regs_exact() Kumar Kartikeya Dwivedi
2026-09-19 2:55 ` bot+bpf-ci
2026-09-19 1:42 ` [PATCH bpf v4 2/2] selftests/bpf: Cover frame changes in bounded loops Kumar Kartikeya Dwivedi
2026-09-19 5:30 ` 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=178979580765.1275551.2384650495430969417.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 \
--cc=npc@anthropic.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