From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH bpf-next 5/5] selftests/bpf: Remove may_goto tests from DENYLIST.s390x
Date: Thu, 21 Aug 2025 12:23:41 +0200 [thread overview]
Message-ID: <20250821103256.291412-6-iii@linux.ibm.com> (raw)
In-Reply-To: <20250821103256.291412-1-iii@linux.ibm.com>
The may_goto instruction is now fully supported on s390x, including the
timed implementation, so remove the respective test from the denylist.
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
---
tools/testing/selftests/bpf/DENYLIST.s390x | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/DENYLIST.s390x b/tools/testing/selftests/bpf/DENYLIST.s390x
index 3ebd77206f98..a17baf8c6fd7 100644
--- a/tools/testing/selftests/bpf/DENYLIST.s390x
+++ b/tools/testing/selftests/bpf/DENYLIST.s390x
@@ -2,4 +2,3 @@
# Alphabetical order
get_stack_raw_tp # user_stack corrupted user stack (no backchain userspace)
stacktrace_build_id # compare_map_keys stackid_hmap vs. stackmap err -2 errno 2 (?)
-verifier_iterating_callbacks
--
2.50.1
prev parent reply other threads:[~2025-08-21 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 10:23 [PATCH bpf-next 0/5] s390/bpf: Add s390 JIT support for timed may_goto Ilya Leoshkevich
2025-08-21 10:23 ` [PATCH bpf-next 1/5] " Ilya Leoshkevich
2025-08-21 10:23 ` [PATCH bpf-next 2/5] selftests/bpf: Add a missing newline to the "bad arch spec" message Ilya Leoshkevich
2025-08-21 10:23 ` [PATCH bpf-next 3/5] selftests/bpf: Add __arch_s390x macro Ilya Leoshkevich
2025-08-21 10:23 ` [PATCH bpf-next 4/5] selftests/bpf: Enable timed may_goto verifier tests on s390x Ilya Leoshkevich
2025-08-21 10:23 ` Ilya Leoshkevich [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=20250821103256.291412-6-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).