BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2 bpf-next 00/13] BPF register bounds range vs range support
Date: Wed, 15 Nov 2023 20:30:25 +0000	[thread overview]
Message-ID: <170008022598.32180.10391937319281894463.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231112010609.848406-1-andrii@kernel.org>

Hello:

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

On Sat, 11 Nov 2023 17:05:56 -0800 you wrote:
> This patch set is a continuation of work started in [0]. It adds a big set of
> manual, auto-generated, and now also random test cases validating BPF
> verifier's register bounds tracking and deduction logic.
> 
> First few patches generalize verifier's logic to handle conditional jumps and
> corresponding range adjustments in case when two non-const registers are
> compared to each other. Patch #1 generalizes reg_set_min_max() portion, while
> patch #2 does the same for is_branch_taken() part of the overall solution.
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,01/13] bpf: generalize reg_set_min_max() to handle non-const register comparisons
    https://git.kernel.org/bpf/bpf-next/c/67420501e868
  - [v2,bpf-next,02/13] bpf: generalize is_scalar_branch_taken() logic
    https://git.kernel.org/bpf/bpf-next/c/96381879a370
  - [v2,bpf-next,03/13] bpf: enhance BPF_JEQ/BPF_JNE is_branch_taken logic
    https://git.kernel.org/bpf/bpf-next/c/be41a203bb9e
  - [v2,bpf-next,04/13] bpf: add register bounds sanity checks and sanitization
    https://git.kernel.org/bpf/bpf-next/c/5f99f312bd3b
  - [v2,bpf-next,05/13] bpf: remove redundant s{32,64} -> u{32,64} deduction logic
    https://git.kernel.org/bpf/bpf-next/c/3cf98cf594ea
  - [v2,bpf-next,06/13] bpf: make __reg{32,64}_deduce_bounds logic more robust
    https://git.kernel.org/bpf/bpf-next/c/cf5fe3c71c5a
  - [v2,bpf-next,07/13] selftests/bpf: BPF register range bounds tester
    https://git.kernel.org/bpf/bpf-next/c/8863238993e2
  - [v2,bpf-next,08/13] selftests/bpf: adjust OP_EQ/OP_NE handling to use subranges for branch taken
    https://git.kernel.org/bpf/bpf-next/c/774f94c5e74d
  - [v2,bpf-next,09/13] selftests/bpf: add range x range test to reg_bounds
    https://git.kernel.org/bpf/bpf-next/c/2b0d204e368b
  - [v2,bpf-next,10/13] selftests/bpf: add randomized reg_bounds tests
    https://git.kernel.org/bpf/bpf-next/c/dab16659c50e
  - [v2,bpf-next,11/13] selftests/bpf: set BPF_F_TEST_SANITY_SCRIPT by default
    https://git.kernel.org/bpf/bpf-next/c/8c5677f8b31e
  - [v2,bpf-next,12/13] veristat: add ability to set BPF_F_TEST_SANITY_STRICT flag with -r flag
    https://git.kernel.org/bpf/bpf-next/c/a5c57f81eb2b
  - [v2,bpf-next,13/13] selftests/bpf: add iter test requiring range x range logic
    https://git.kernel.org/bpf/bpf-next/c/882e3d873c2d

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



      parent reply	other threads:[~2023-11-15 20:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12  1:05 [PATCH v2 bpf-next 00/13] BPF register bounds range vs range support Andrii Nakryiko
2023-11-12  1:05 ` [PATCH v2 bpf-next 01/13] bpf: generalize reg_set_min_max() to handle non-const register comparisons Andrii Nakryiko
2023-11-13  4:35   ` Shung-Hsi Yu
2023-11-12  1:05 ` [PATCH v2 bpf-next 02/13] bpf: generalize is_scalar_branch_taken() logic Andrii Nakryiko
2023-11-13  4:46   ` Shung-Hsi Yu
2023-11-12  1:05 ` [PATCH v2 bpf-next 03/13] bpf: enhance BPF_JEQ/BPF_JNE is_branch_taken logic Andrii Nakryiko
2023-11-12  1:06 ` [PATCH v2 bpf-next 04/13] bpf: add register bounds sanity checks and sanitization Andrii Nakryiko
2023-11-13  4:53   ` Shung-Hsi Yu
2023-11-15 20:25   ` Alexei Starovoitov
2023-11-15 22:06     ` Andrii Nakryiko
2023-11-16 19:37       ` Alexei Starovoitov
2023-11-12  1:06 ` [PATCH v2 bpf-next 05/13] bpf: remove redundant s{32,64} -> u{32,64} deduction logic Andrii Nakryiko
2023-11-12  1:06 ` [PATCH v2 bpf-next 06/13] bpf: make __reg{32,64}_deduce_bounds logic more robust Andrii Nakryiko
2023-11-12  1:06 ` [PATCH v2 bpf-next 07/13] selftests/bpf: BPF register range bounds tester Andrii Nakryiko
2023-11-13  4:55   ` Shung-Hsi Yu
2023-11-12  1:06 ` [PATCH v2 bpf-next 08/13] selftests/bpf: adjust OP_EQ/OP_NE handling to use subranges for branch taken Andrii Nakryiko
2023-11-13 23:46   ` Eduard Zingerman
2023-11-12  1:06 ` [PATCH v2 bpf-next 09/13] selftests/bpf: add range x range test to reg_bounds Andrii Nakryiko
2023-11-12  1:06 ` [PATCH v2 bpf-next 10/13] selftests/bpf: add randomized reg_bounds tests Andrii Nakryiko
2023-11-19 19:53   ` Alexei Starovoitov
2023-11-12  1:06 ` [PATCH v2 bpf-next 11/13] selftests/bpf: set BPF_F_TEST_SANITY_SCRIPT by default Andrii Nakryiko
2023-11-12  1:06 ` [PATCH v2 bpf-next 12/13] veristat: add ability to set BPF_F_TEST_SANITY_STRICT flag with -r flag Andrii Nakryiko
2023-11-12  1:06 ` [PATCH v2 bpf-next 13/13] selftests/bpf: add iter test requiring range x range logic Andrii Nakryiko
2023-11-15 20:30 ` 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=170008022598.32180.10391937319281894463.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@meta.com \
    --cc=martin.lau@kernel.org \
    /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