Re: [PATCH v6 bpf-next 00/17] BPF register bounds logic and testing improvements

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 1 Nov 2023 20:37:42 -0700 you wrote:
> This patch set adds a big set of manual and auto-generated test cases
> validating BPF verifier's register bounds tracking and deduction logic. See
> details in the last patch.
> 
> We start with building a tester that validates existing <range> vs <scalar>
> verifier logic for range bounds. To make all this work, BPF verifier's logic
> needed a bunch of improvements to handle some cases that previously were not
> covered. This had no implications as to correctness of verifier logic, but it
> was incomplete enough to cause significant disagreements with alternative
> implementation of register bounds logic that tests in this patch set
> implement. So we need BPF verifier logic improvements to make all the tests
> pass. This is what we do in patches #3 through #9.
> 
> [...]

Here is the summary with links:
  - [v6,bpf-next,01/17] selftests/bpf: fix RELEASE=1 build for tc_opts
    https://git.kernel.org/bpf/bpf-next/c/3cda0779ded1
  - [v6,bpf-next,02/17] selftests/bpf: satisfy compiler by having explicit return in btf test
    https://git.kernel.org/bpf/bpf-next/c/7bcc07dcd835
  - [v6,bpf-next,03/17] bpf: derive smin/smax from umin/max bounds
    https://git.kernel.org/bpf/bpf-next/c/2e74aef782d3
  - [v6,bpf-next,04/17] bpf: derive smin32/smax32 from umin32/umax32 bounds
    https://git.kernel.org/bpf/bpf-next/c/f188765f23a5
  - [v6,bpf-next,05/17] bpf: derive subreg bounds from full bounds when upper 32 bits are constant
    https://git.kernel.org/bpf/bpf-next/c/f404ef3b42c8
  - [v6,bpf-next,06/17] bpf: add special smin32/smax32 derivation from 64-bit bounds
    https://git.kernel.org/bpf/bpf-next/c/6533e0acff58
  - [v6,bpf-next,07/17] bpf: improve deduction of 64-bit bounds from 32-bit bounds
    https://git.kernel.org/bpf/bpf-next/c/3d6940ddd9b5
  - [v6,bpf-next,08/17] bpf: try harder to deduce register bounds from different numeric domains
    https://git.kernel.org/bpf/bpf-next/c/558c06e551a3
  - [v6,bpf-next,09/17] bpf: drop knowledge-losing __reg_combine_{32,64}_into_{64,32} logic
    https://git.kernel.org/bpf/bpf-next/c/b929d4979b2b
  - [v6,bpf-next,10/17] selftests/bpf: BPF register range bounds tester
    (no matching commit)
  - [v6,bpf-next,11/17] bpf: rename is_branch_taken reg arguments to prepare for the second one
    https://git.kernel.org/bpf/bpf-next/c/cdeb5dab9238
  - [v6,bpf-next,12/17] bpf: generalize is_branch_taken() to work with two registers
    https://git.kernel.org/bpf/bpf-next/c/fc3615dd0ee9
  - [v6,bpf-next,13/17] bpf: move is_branch_taken() down
    https://git.kernel.org/bpf/bpf-next/c/dd2a2cc3c1bf
  - [v6,bpf-next,14/17] bpf: generalize is_branch_taken to handle all conditional jumps in one place
    https://git.kernel.org/bpf/bpf-next/c/171de12646d2
  - [v6,bpf-next,15/17] bpf: unify 32-bit and 64-bit is_branch_taken logic
    https://git.kernel.org/bpf/bpf-next/c/761a9e560d0c
  - [v6,bpf-next,16/17] bpf: prepare reg_set_min_max for second set of registers
    https://git.kernel.org/bpf/bpf-next/c/4c617286771e
  - [v6,bpf-next,17/17] bpf: generalize reg_set_min_max() to handle two sets of two registers
    https://git.kernel.org/bpf/bpf-next/c/9a14d62a2cdb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html