From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org
Cc: kernel-team@meta.com
Subject: Re: [PATCH v2 bpf-next 08/13] selftests/bpf: adjust OP_EQ/OP_NE handling to use subranges for branch taken
Date: Tue, 14 Nov 2023 01:46:02 +0200 [thread overview]
Message-ID: <eb050694397f7679c52dcad85153a0d8f2fe7cbc.camel@gmail.com> (raw)
In-Reply-To: <20231112010609.848406-9-andrii@kernel.org>
On Sat, 2023-11-11 at 17:06 -0800, Andrii Nakryiko wrote:
> Similar to kernel-side BPF verifier logic enhancements, use 32-bit
> subrange knowledge for is_branch_taken() logic in reg_bounds selftests.
>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
next prev parent reply other threads:[~2023-11-13 23:46 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 [this message]
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 ` [PATCH v2 bpf-next 00/13] BPF register bounds range vs range support patchwork-bot+netdevbpf
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=eb050694397f7679c52dcad85153a0d8f2fe7cbc.camel@gmail.com \
--to=eddyz87@gmail.com \
--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