Re: [PATCH v4 bpf-next 0/7] BPF register bounds logic and testing improvements

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Sun, 22 Oct 2023 13:57:36 -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.
> 
> To make this approach 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.
> 
> [...]

Here is the summary with links:
  - [v4,bpf-next,1/7] bpf: improve JEQ/JNE branch taken logic
    https://git.kernel.org/bpf/bpf-next/c/42d31dd601fa
  - [v4,bpf-next,2/7] bpf: derive smin/smax from umin/max bounds
    (no matching commit)
  - [v4,bpf-next,3/7] bpf: enhance subregister bounds deduction logic
    (no matching commit)
  - [v4,bpf-next,4/7] bpf: improve deduction of 64-bit bounds from 32-bit bounds
    (no matching commit)
  - [v4,bpf-next,5/7] bpf: try harder to deduce register bounds from different numeric domains
    (no matching commit)
  - [v4,bpf-next,6/7] bpf: drop knowledge-losing __reg_combine_{32,64}_into_{64,32} logic
    (no matching commit)
  - [v4,bpf-next,7/7] selftests/bpf: BPF register range bounds tester
    (no matching commit)

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