From: Menglong Dong <menglong8.dong@gmail.com>
To: andrii@kernel.org, yonghong.song@linux.dev
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
martin.lau@linux.dev, song@kernel.org, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
Menglong Dong <menglong8.dong@gmail.com>
Subject: [PATCH net-next v2 2/2] selftests/bpf: activate the OP_NE login in range_cond()
Date: Tue, 12 Dec 2023 21:10:31 +0800 [thread overview]
Message-ID: <20231212131031.3088661-3-menglong8.dong@gmail.com> (raw)
In-Reply-To: <20231212131031.3088661-1-menglong8.dong@gmail.com>
The edge range checking for the registers is supported by the verifier
now, so we can activate the extended login in
tools/testing/selftests/bpf/prog_tests/reg_bounds.c/range_cond() to test
such logic.
Signed-off-by: Menglong Dong <menglong8.dong@gmail.com>
---
tools/testing/selftests/bpf/prog_tests/reg_bounds.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/tools/testing/selftests/bpf/prog_tests/reg_bounds.c b/tools/testing/selftests/bpf/prog_tests/reg_bounds.c
index 0c9abd279e18..49d8d4bafe99 100644
--- a/tools/testing/selftests/bpf/prog_tests/reg_bounds.c
+++ b/tools/testing/selftests/bpf/prog_tests/reg_bounds.c
@@ -590,12 +590,7 @@ static void range_cond(enum num_t t, struct range x, struct range y,
*newy = range(t, max_t(t, x.a, y.a), min_t(t, x.b, y.b));
break;
case OP_NE:
- /* generic case, can't derive more information */
- *newx = range(t, x.a, x.b);
- *newy = range(t, y.a, y.b);
- break;
-
- /* below extended logic is not supported by verifier just yet */
+ /* below logic is supported by the verifier now */
if (x.a == x.b && x.a == y.a) {
/* X is a constant matching left side of Y */
*newx = range(t, x.a, x.b);
--
2.39.2
next prev parent reply other threads:[~2023-12-12 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 13:10 [PATCH net-next v2 0/2] bpf: support to trace BPF_JNE Menglong Dong
2023-12-12 13:10 ` [PATCH net-next v2 1/2] bpf: make the verifier trace the "not qeual" for regs Menglong Dong
2023-12-12 23:23 ` Eduard Zingerman
2023-12-13 2:11 ` Menglong Dong
2023-12-12 13:10 ` Menglong Dong [this message]
2023-12-12 23:37 ` [PATCH net-next v2 2/2] selftests/bpf: activate the OP_NE login in range_cond() Eduard Zingerman
2023-12-13 2:35 ` Menglong Dong
2023-12-13 0:00 ` [PATCH net-next v2 0/2] bpf: support to trace BPF_JNE Andrii Nakryiko
2023-12-13 2:05 ` Menglong Dong
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=20231212131031.3088661-3-menglong8.dong@gmail.com \
--to=menglong8.dong@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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