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 bpf-next 0/7] BPF verifier state equivalence checks improvements
Date: Wed, 28 Dec 2022 02:10:16 +0000 [thread overview]
Message-ID: <167219341607.26190.4724859434610356280.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221223054921.958283-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 22 Dec 2022 21:49:14 -0800 you wrote:
> This patch set fixes, improves, and refactors parts of BPF verifier's state
> equivalence checks.
>
> Patch #1 fixes refsafe(), making it take into account ID map when comparing
> reference IDs. See patch for details.
>
> Patches #2-#7 refactor regsafe() function which compares two register states
> across old and current states. regsafe() is critical piece of logic, so to
> make it easier to review and validate refactorings and logic fixes and
> improvements, each patch makes a small change, explaining why the change is
> correct and makes sense. Please see individual patches for details.
>
> [...]
Here is the summary with links:
- [bpf-next,1/7] bpf: teach refsafe() to take into account ID remapping
https://git.kernel.org/bpf/bpf-next/c/e8f55fcf7779
- [bpf-next,2/7] bpf: reorganize struct bpf_reg_state fields
https://git.kernel.org/bpf/bpf-next/c/a73bf9f2d969
- [bpf-next,3/7] bpf: generalize MAYBE_NULL vs non-MAYBE_NULL rule
https://git.kernel.org/bpf/bpf-next/c/7f4ce97cd5ed
- [bpf-next,4/7] bpf: reject non-exact register type matches in regsafe()
https://git.kernel.org/bpf/bpf-next/c/910f69996674
- [bpf-next,5/7] bpf: perform byte-by-byte comparison only when necessary in regsafe()
https://git.kernel.org/bpf/bpf-next/c/4a95c85c9948
- [bpf-next,6/7] bpf: fix regs_exact() logic in regsafe() to remap IDs correctly
https://git.kernel.org/bpf/bpf-next/c/4633a0068258
- [bpf-next,7/7] bpf: unify PTR_TO_MAP_{KEY,VALUE} with default case in regsafe()
(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:[~2022-12-28 2:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 5:49 [PATCH bpf-next 0/7] BPF verifier state equivalence checks improvements Andrii Nakryiko
2022-12-23 5:49 ` [PATCH bpf-next 1/7] bpf: teach refsafe() to take into account ID remapping Andrii Nakryiko
2022-12-23 5:49 ` [PATCH bpf-next 2/7] bpf: reorganize struct bpf_reg_state fields Andrii Nakryiko
2022-12-23 5:49 ` [PATCH bpf-next 3/7] bpf: generalize MAYBE_NULL vs non-MAYBE_NULL rule Andrii Nakryiko
2022-12-23 5:49 ` [PATCH bpf-next 4/7] bpf: reject non-exact register type matches in regsafe() Andrii Nakryiko
2022-12-23 5:49 ` [PATCH bpf-next 5/7] bpf: perform byte-by-byte comparison only when necessary " Andrii Nakryiko
2022-12-23 5:49 ` [PATCH bpf-next 6/7] bpf: fix regs_exact() logic in regsafe() to remap IDs correctly Andrii Nakryiko
2022-12-23 5:49 ` [PATCH bpf-next 7/7] bpf: unify PTR_TO_MAP_{KEY,VALUE} with default case in regsafe() Andrii Nakryiko
2022-12-28 2:00 ` Alexei Starovoitov
2022-12-29 21:59 ` Andrii Nakryiko
2022-12-30 2:19 ` Alexei Starovoitov
2023-01-03 22:04 ` Andrii Nakryiko
2023-01-04 22:35 ` Alexei Starovoitov
2023-01-04 23:03 ` Andrii Nakryiko
2023-01-05 0:14 ` Alexei Starovoitov
2023-01-11 19:08 ` Andrii Nakryiko
2022-12-28 2:10 ` 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=167219341607.26190.4724859434610356280.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox