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 v3 0/6] Improvements for tracking scalars in the BPF verifier
Date: Fri, 02 Feb 2024 21:30:29 +0000 [thread overview]
Message-ID: <170690942904.20598.1069790224577035855.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240127175237.526726-1-maxtram95@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel•org>:
On Sat, 27 Jan 2024 19:52:31 +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,v3,1/6] bpf: Track spilled unbounded scalars
https://git.kernel.org/bpf/bpf-next/c/e67ddd9b1cff
- [bpf-next,v3,2/6] selftests/bpf: Test tracking spilled unbounded scalars
https://git.kernel.org/bpf/bpf-next/c/6be503cec6c9
- [bpf-next,v3,3/6] bpf: Preserve boundaries and track scalars on narrowing fill
https://git.kernel.org/bpf/bpf-next/c/c1e6148cb4f8
- [bpf-next,v3,4/6] selftests/bpf: Add test cases for narrowing fill
https://git.kernel.org/bpf/bpf-next/c/067313a85c6f
- [bpf-next,v3,5/6] bpf: handle scalar spill vs all MISC in stacksafe()
https://git.kernel.org/bpf/bpf-next/c/6efbde200bf3
- [bpf-next,v3,6/6] selftests/bpf: states pruning checks for scalar vs STACK_MISC
https://git.kernel.org/bpf/bpf-next/c/73a28d9d000e
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-02-02 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 17:52 [PATCH bpf-next v3 0/6] Improvements for tracking scalars in the BPF verifier Maxim Mikityanskiy
2024-01-27 17:52 ` [PATCH bpf-next v3 1/6] bpf: Track spilled unbounded scalars Maxim Mikityanskiy
2024-01-27 17:52 ` [PATCH bpf-next v3 2/6] selftests/bpf: Test tracking " Maxim Mikityanskiy
2024-01-27 17:52 ` [PATCH bpf-next v3 3/6] bpf: Preserve boundaries and track scalars on narrowing fill Maxim Mikityanskiy
2024-01-27 17:52 ` [PATCH bpf-next v3 4/6] selftests/bpf: Add test cases for " Maxim Mikityanskiy
2024-01-27 17:52 ` [PATCH bpf-next v3 5/6] bpf: handle scalar spill vs all MISC in stacksafe() Maxim Mikityanskiy
2024-01-27 17:52 ` [PATCH bpf-next v3 6/6] selftests/bpf: states pruning checks for scalar vs STACK_MISC Maxim Mikityanskiy
2024-02-02 21: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=170690942904.20598.1069790224577035855.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=eddyz87@gmail$(echo .)com \
--cc=haoluo@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kpsingh@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=martin.lau@linux$(echo .)dev \
--cc=maxim@isovalent$(echo .)com \
--cc=maxtram95@gmail$(echo .)com \
--cc=mykolal@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sdf@google$(echo .)com \
--cc=shuah@kernel$(echo .)org \
--cc=shung-hsi.yu@suse$(echo .)com \
--cc=song@kernel$(echo .)org \
--cc=yonghong.song@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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