From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 0/6] BPF verifier precision tracking improvements
Date: Fri, 04 Nov 2022 19:00:17 +0000 [thread overview]
Message-ID: <166758841795.26959.16340729986307349960.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221104163649.121784-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 4 Nov 2022 09:36:43 -0700 you wrote:
> This patch set fixes and improves BPF verifier's precision tracking logic for
> SCALAR registers.
>
> Patches #1 and #2 are bug fixes discovered while working on these changes.
>
> Patch #3 enables precision tracking for BPF programs that contain subprograms.
> This was disabled before and prevent any modern BPF programs that use
> subprograms from enjoying the benefits of SCALAR (im)precise logic.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/6] bpf: propagate precision in ALU/ALU64 operations
https://git.kernel.org/bpf/bpf-next/c/a3b666bfa9c9
- [v2,bpf-next,2/6] bpf: propagate precision across all frames, not just the last one
https://git.kernel.org/bpf/bpf-next/c/529409ea92d5
- [v2,bpf-next,3/6] bpf: allow precision tracking for programs with subprogs
https://git.kernel.org/bpf/bpf-next/c/be2ef8161572
- [v2,bpf-next,4/6] bpf: stop setting precise in current state
https://git.kernel.org/bpf/bpf-next/c/f63181b6ae79
- [v2,bpf-next,5/6] bpf: aggressively forget precise markings during state checkpointing
https://git.kernel.org/bpf/bpf-next/c/7a830b53c17b
- [v2,bpf-next,6/6] selftests/bpf: make test_align selftest more robust
https://git.kernel.org/bpf/bpf-next/c/4f999b767769
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:[~2022-11-04 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 16:36 [PATCH v2 bpf-next 0/6] BPF verifier precision tracking improvements Andrii Nakryiko
2022-11-04 16:36 ` [PATCH v2 bpf-next 1/6] bpf: propagate precision in ALU/ALU64 operations Andrii Nakryiko
2022-11-04 16:36 ` [PATCH v2 bpf-next 2/6] bpf: propagate precision across all frames, not just the last one Andrii Nakryiko
2022-11-04 16:36 ` [PATCH v2 bpf-next 3/6] bpf: allow precision tracking for programs with subprogs Andrii Nakryiko
2022-11-04 16:36 ` [PATCH v2 bpf-next 4/6] bpf: stop setting precise in current state Andrii Nakryiko
2024-01-24 10:06 ` Stefan Fleischmann
2024-01-24 12:38 ` Stefan Fleischmann
2022-11-04 16:36 ` [PATCH v2 bpf-next 5/6] bpf: aggressively forget precise markings during state checkpointing Andrii Nakryiko
2022-11-04 16:36 ` [PATCH v2 bpf-next 6/6] selftests/bpf: make test_align selftest more robust Andrii Nakryiko
2022-11-04 19: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=166758841795.26959.16340729986307349960.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=kernel-team@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.