From: patchwork-bot+netdevbpf@kernel.org
To: Maxim Mikityanskiy <maxtram95@gmail.com>
Cc: eddyz87@gmail.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, shung-hsi.yu@suse.com,
john.fastabend@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
shuah@kernel.org, davem@davemloft.net, kuba@kernel.org,
hawk@kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
maxim@isovalent.com
Subject: Re: [PATCH bpf-next v2 00/15] Improvements for tracking scalars in the BPF verifier
Date: Fri, 12 Jan 2024 03:00:46 +0000 [thread overview]
Message-ID: <170502844684.24601.17326225284234857035.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240108205209.838365-1-maxtram95@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 8 Jan 2024 22:51:54 +0200 you wrote:
> From: Maxim Mikityanskiy <maxim@isovalent.com>
>
> The goal of this series is to extend the verifier's capabilities of
> tracking scalars when they are spilled to stack, especially when the
> spill or fill is narrowing. It also contains a fix by Eduard for
> infinite loop detection and a state pruning optimization by Eduard that
> compensates for a verification complexity regression introduced by
> tracking unbounded scalars. These improvements reduce the surface of
> false rejections that I saw while working on Cilium codebase.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,01/15] selftests/bpf: Fix the u64_offset_to_skb_data test
https://git.kernel.org/bpf/bpf-next/c/02fb00d34de1
- [bpf-next,v2,02/15] bpf: make infinite loop detection in is_state_visited() exact
https://git.kernel.org/bpf/bpf-next/c/3a96c705f48a
- [bpf-next,v2,03/15] selftests/bpf: check if imprecise stack spills confuse infinite loop detection
https://git.kernel.org/bpf/bpf-next/c/723909ae6496
- [bpf-next,v2,04/15] bpf: Make bpf_for_each_spilled_reg consider narrow spills
https://git.kernel.org/bpf/bpf-next/c/0e00a9551c61
- [bpf-next,v2,05/15] selftests/bpf: Add a test case for 32-bit spill tracking
https://git.kernel.org/bpf/bpf-next/c/221dffec93e8
- [bpf-next,v2,06/15] bpf: Add the assign_scalar_id_before_mov function
https://git.kernel.org/bpf/bpf-next/c/85b6e9d75c8e
- [bpf-next,v2,07/15] bpf: Add the get_reg_width function
https://git.kernel.org/bpf/bpf-next/c/b08973e4d9c4
- [bpf-next,v2,08/15] bpf: Assign ID to scalars on spill
https://git.kernel.org/bpf/bpf-next/c/26b560765e67
- [bpf-next,v2,09/15] selftests/bpf: Test assigning ID to scalars on spill
https://git.kernel.org/bpf/bpf-next/c/5a052eb509e9
- [bpf-next,v2,10/15] bpf: Track spilled unbounded scalars
https://git.kernel.org/bpf/bpf-next/c/53ac20c9e0dd
- [bpf-next,v2,11/15] selftests/bpf: Test tracking spilled unbounded scalars
https://git.kernel.org/bpf/bpf-next/c/9ba80a06cabb
- [bpf-next,v2,12/15] bpf: Preserve boundaries and track scalars on narrowing fill
(no matching commit)
- [bpf-next,v2,13/15] selftests/bpf: Add test cases for narrowing fill
(no matching commit)
- [bpf-next,v2,14/15] bpf: Optimize state pruning for spilled scalars
(no matching commit)
- [bpf-next,v2,15/15] selftests/bpf: states pruning checks for scalar vs STACK_{MISC,ZERO}
(no matching commit)
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:[~2024-01-12 3:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 20:51 [PATCH bpf-next v2 00/15] Improvements for tracking scalars in the BPF verifier Maxim Mikityanskiy
2024-01-08 20:51 ` [PATCH bpf-next v2 01/15] selftests/bpf: Fix the u64_offset_to_skb_data test Maxim Mikityanskiy
2024-01-08 20:51 ` [PATCH bpf-next v2 02/15] bpf: make infinite loop detection in is_state_visited() exact Maxim Mikityanskiy
2024-01-08 20:51 ` [PATCH bpf-next v2 03/15] selftests/bpf: check if imprecise stack spills confuse infinite loop detection Maxim Mikityanskiy
2024-01-08 20:51 ` [PATCH bpf-next v2 04/15] bpf: Make bpf_for_each_spilled_reg consider narrow spills Maxim Mikityanskiy
2024-01-08 20:51 ` [PATCH bpf-next v2 05/15] selftests/bpf: Add a test case for 32-bit spill tracking Maxim Mikityanskiy
2024-01-08 20:52 ` [PATCH bpf-next v2 06/15] bpf: Add the assign_scalar_id_before_mov function Maxim Mikityanskiy
2024-01-08 20:52 ` [PATCH bpf-next v2 07/15] bpf: Add the get_reg_width function Maxim Mikityanskiy
2024-01-08 20:52 ` [PATCH bpf-next v2 08/15] bpf: Assign ID to scalars on spill Maxim Mikityanskiy
2024-01-08 20:52 ` [PATCH bpf-next v2 09/15] selftests/bpf: Test assigning " Maxim Mikityanskiy
2024-01-09 23:34 ` Andrii Nakryiko
2024-01-08 20:52 ` [PATCH bpf-next v2 10/15] bpf: Track spilled unbounded scalars Maxim Mikityanskiy
2024-01-12 19:10 ` Alexei Starovoitov
2024-01-12 20:44 ` Maxim Mikityanskiy
2024-01-12 20:50 ` Alexei Starovoitov
2024-01-08 20:52 ` [PATCH bpf-next v2 11/15] selftests/bpf: Test tracking " Maxim Mikityanskiy
2024-01-08 20:52 ` [PATCH bpf-next v2 12/15] bpf: Preserve boundaries and track scalars on narrowing fill Maxim Mikityanskiy
2024-01-09 23:51 ` Andrii Nakryiko
2024-01-08 20:52 ` [PATCH bpf-next v2 13/15] selftests/bpf: Add test cases for " Maxim Mikityanskiy
2024-01-09 23:55 ` Andrii Nakryiko
2024-01-08 20:52 ` [PATCH bpf-next v2 14/15] bpf: Optimize state pruning for spilled scalars Maxim Mikityanskiy
2024-01-10 0:22 ` Andrii Nakryiko
2024-01-10 21:04 ` Eduard Zingerman
2024-01-10 21:52 ` Andrii Nakryiko
2024-01-08 20:52 ` [PATCH bpf-next v2 15/15] selftests/bpf: states pruning checks for scalar vs STACK_{MISC,ZERO} Maxim Mikityanskiy
2024-01-10 0:27 ` Andrii Nakryiko
2024-01-10 20:27 ` Eduard Zingerman
2024-01-12 3:00 ` 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=170502844684.24601.17326225284234857035.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=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=maxim@isovalent.com \
--cc=maxtram95@gmail.com \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=shung-hsi.yu@suse.com \
--cc=song@kernel.org \
--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