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, kernel-team@fb.com, yhs@fb.com,
memxor@gmail.com, ecree.xilinx@gmail.com
Subject: Re: [PATCH bpf-next 0/7] stricter register ID checking in regsafe()
Date: Sat, 10 Dec 2022 21:50:17 +0000 [thread overview]
Message-ID: <167070901705.12059.17423131126807625637.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209135733.28851-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 9 Dec 2022 15:57:26 +0200 you wrote:
> This patch-set consists of a series of bug fixes for register ID
> tracking in verifier.c:states_equal()/regsafe() functions:
> - for registers of type PTR_TO_MAP_{KEY,VALUE}, PTR_TO_PACKET[_META]
> the regsafe() should call check_ids() even if registers are
> byte-to-byte equal;
> - states_equal() must maintain idmap that covers all function frames
> in the state because functions like mark_ptr_or_null_regs() operate
> on all registers in the state;
> - regsafe() must compare spin lock ids for PTR_TO_MAP_VALUE registers.
>
> [...]
Here is the summary with links:
- [bpf-next,1/7] bpf: regsafe() must not skip check_ids()
https://git.kernel.org/bpf/bpf-next/c/7c884339bbff
- [bpf-next,2/7] selftests/bpf: test cases for regsafe() bug skipping check_id()
https://git.kernel.org/bpf/bpf-next/c/cb578c1c9cf6
- [bpf-next,3/7] bpf: states_equal() must build idmap for all function frames
https://git.kernel.org/bpf/bpf-next/c/5dd9cdbc9dec
- [bpf-next,4/7] selftests/bpf: verify states_equal() maintains idmap across all frames
https://git.kernel.org/bpf/bpf-next/c/7d0579433087
- [bpf-next,5/7] bpf: use check_ids() for active_lock comparison
https://git.kernel.org/bpf/bpf-next/c/4ea2bb158bec
- [bpf-next,6/7] selftests/bpf: Add pruning test case for bpf_spin_lock
https://git.kernel.org/bpf/bpf-next/c/2026f2062df8
- [bpf-next,7/7] selftests/bpf: test case for relaxed prunning of active_lock.id
https://git.kernel.org/bpf/bpf-next/c/efd6286ff74a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-12-10 21:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 13:57 [PATCH bpf-next 0/7] stricter register ID checking in regsafe() Eduard Zingerman
2022-12-09 13:57 ` [PATCH bpf-next 1/7] bpf: regsafe() must not skip check_ids() Eduard Zingerman
2022-12-14 0:35 ` Andrii Nakryiko
2022-12-14 13:25 ` Eduard Zingerman
2022-12-14 19:37 ` Andrii Nakryiko
2022-12-09 13:57 ` [PATCH bpf-next 2/7] selftests/bpf: test cases for regsafe() bug skipping check_id() Eduard Zingerman
2022-12-09 13:57 ` [PATCH bpf-next 3/7] bpf: states_equal() must build idmap for all function frames Eduard Zingerman
2022-12-14 0:35 ` Andrii Nakryiko
2022-12-14 15:33 ` Eduard Zingerman
2022-12-14 17:24 ` Andrii Nakryiko
2022-12-09 13:57 ` [PATCH bpf-next 4/7] selftests/bpf: verify states_equal() maintains idmap across all frames Eduard Zingerman
2022-12-14 0:35 ` Andrii Nakryiko
2022-12-14 16:38 ` Eduard Zingerman
2022-12-14 17:10 ` Andrii Nakryiko
2022-12-09 13:57 ` [PATCH bpf-next 5/7] bpf: use check_ids() for active_lock comparison Eduard Zingerman
2022-12-09 13:57 ` [PATCH bpf-next 6/7] selftests/bpf: Add pruning test case for bpf_spin_lock Eduard Zingerman
2022-12-10 21:45 ` Alexei Starovoitov
2022-12-09 13:57 ` [PATCH bpf-next 7/7] selftests/bpf: test case for relaxed prunning of active_lock.id Eduard Zingerman
2022-12-10 21:50 ` patchwork-bot+netdevbpf [this message]
2022-12-14 0:34 ` [PATCH bpf-next 0/7] stricter register ID checking in regsafe() Andrii Nakryiko
2022-12-14 16:28 ` Eduard Zingerman
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=167070901705.12059.17423131126807625637.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=ecree.xilinx@gmail.com \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=memxor@gmail.com \
--cc=yhs@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