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, memxor@gmail.com
Subject: Re: [PATCH bpf 00/10] bpf: add missing precision propagation after bpf_register_is_null calls
Date: Sat, 05 Sep 2026 01:20:20 +0000 [thread overview]
Message-ID: <178857122039.1047271.17751024419566077235.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904-register-is-null-precise-fixes-v1-0-0f5a360ff15d@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 4 Sep 2026 17:05:51 -0700 you wrote:
> Fix [1] uncovered a host of locations where the call to
> bpf_register_is_null() is not followed by a call to
> bpf_mark_chain_precision().
>
> check_map_kptr_access() is omitted as it is handled [2]
> by another series.
>
> [...]
Here is the summary with links:
- [bpf,01/10] bpf: mark a NULL call argument precise
https://git.kernel.org/bpf/bpf/c/1a3a10b030c9
- [bpf,02/10] selftests/bpf: precision of a NULL helper argument
https://git.kernel.org/bpf/bpf/c/593c8eb0fb91
- [bpf,03/10] bpf: mark a NULL memory argument of a call precise
https://git.kernel.org/bpf/bpf/c/f1e418129f2e
- [bpf,04/10] selftests/bpf: precision of a NULL global subprogram memory argument
https://git.kernel.org/bpf/bpf/c/100f4cc0d59b
- [bpf,05/10] bpf: mark a NULL kfunc argument precise
https://git.kernel.org/bpf/bpf/c/506ada89629e
- [bpf,06/10] selftests/bpf: precision of a NULL kfunc argument
https://git.kernel.org/bpf/bpf/c/562d266d3fae
- [bpf,07/10] bpf: mark a NULL BTF_ID argument of a global subprogram precise
https://git.kernel.org/bpf/bpf/c/e726fc6b9afe
- [bpf,08/10] selftests/bpf: precision of a NULL global subprogram BTF_ID argument
https://git.kernel.org/bpf/bpf/c/91957791663f
- [bpf,09/10] bpf: propagate mark_chain_precision() errors out of loop_flag_is_zero()
https://git.kernel.org/bpf/bpf/c/1d7f8f191c06
- [bpf,10/10] bpf: use mark_arg_precision() in check_mem_size_reg()
https://git.kernel.org/bpf/bpf/c/cf2475616b11
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-05 1:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 0:05 [PATCH bpf 00/10] bpf: add missing precision propagation after bpf_register_is_null calls Eduard Zingerman
2026-09-05 0:05 ` [PATCH bpf 01/10] bpf: mark a NULL call argument precise Eduard Zingerman
2026-09-05 0:21 ` sashiko-bot
2026-09-05 0:05 ` [PATCH bpf 02/10] selftests/bpf: precision of a NULL helper argument Eduard Zingerman
2026-09-05 0:05 ` [PATCH bpf 03/10] bpf: mark a NULL memory argument of a call precise Eduard Zingerman
2026-09-05 0:23 ` sashiko-bot
2026-09-05 0:51 ` bot+bpf-ci
2026-09-05 0:05 ` [PATCH bpf 04/10] selftests/bpf: precision of a NULL global subprogram memory argument Eduard Zingerman
2026-09-05 0:51 ` bot+bpf-ci
2026-09-05 0:05 ` [PATCH bpf 05/10] bpf: mark a NULL kfunc argument precise Eduard Zingerman
2026-09-05 0:51 ` bot+bpf-ci
2026-09-05 0:05 ` [PATCH bpf 06/10] selftests/bpf: precision of a NULL kfunc argument Eduard Zingerman
2026-09-05 0:05 ` [PATCH bpf 07/10] bpf: mark a NULL BTF_ID argument of a global subprogram precise Eduard Zingerman
2026-09-05 0:19 ` sashiko-bot
2026-09-05 0:05 ` [PATCH bpf 08/10] selftests/bpf: precision of a NULL global subprogram BTF_ID argument Eduard Zingerman
2026-09-05 0:06 ` [PATCH bpf 09/10] bpf: propagate mark_chain_precision() errors out of loop_flag_is_zero() Eduard Zingerman
2026-09-05 0:06 ` [PATCH bpf 10/10] bpf: use mark_arg_precision() in check_mem_size_reg() Eduard Zingerman
2026-09-05 0:51 ` bot+bpf-ci
2026-09-05 1: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=178857122039.1047271.17751024419566077235.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=memxor@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox