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, emil@etsalapatis.com
Subject: Re: [PATCH bpf v1 1/2] bpf: account for current allocated stack depth in widen_imprecise_scalars()
Date: Fri, 14 Nov 2025 17:57:21 +0000 [thread overview]
Message-ID: <176314304143.1747974.17106695505355310740.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251114025730.772723-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 13 Nov 2025 18:57:29 -0800 you wrote:
> The usage pattern for widen_imprecise_scalars() looks as follows:
>
> prev_st = find_prev_entry(env, ...);
> queued_st = push_stack(...);
> widen_imprecise_scalars(env, prev_st, queued_st);
>
> Where prev_st is an ancestor of the queued_st in the explored states
> tree. This ancestor is not guaranteed to have same allocated stack
> depth as queued_st. E.g. in the following case:
>
> [...]
Here is the summary with links:
- [bpf,v1,1/2] bpf: account for current allocated stack depth in widen_imprecise_scalars()
https://git.kernel.org/bpf/bpf/c/b0c8e6d3d866
- [bpf,v1,2/2] selftests/bpf: widen_imprecise_scalars() and different stack depth
https://git.kernel.org/bpf/bpf/c/6c762611fed7
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:[~2025-11-14 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 2:57 [PATCH bpf v1 1/2] bpf: account for current allocated stack depth in widen_imprecise_scalars() Eduard Zingerman
2025-11-14 2:57 ` [PATCH bpf v1 2/2] selftests/bpf: widen_imprecise_scalars() and different stack depth Eduard Zingerman
2025-11-14 17: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=176314304143.1747974.17106695505355310740.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@fb.com \
--cc=martin.lau@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox