From: Puranjay Mohan <puranjay@kernel.org>
To: Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Mykola Lysenko <mykolal@fb.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, puranjay12@gmail.com
Subject: [PATCH bpf] selftests/bpf: DENYLIST.aarch64: Remove fexit_sleep
Date: Fri, 5 Jul 2024 14:50:09 +0000 [thread overview]
Message-ID: <20240705145009.32340-1-puranjay@kernel.org> (raw)
fexit_sleep test runs successfully now on the CI so remove it from the
deny list.
Signed-off-by: Puranjay Mohan <puranjay@kernel.org>
---
tools/testing/selftests/bpf/DENYLIST.aarch64 | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/DENYLIST.aarch64 b/tools/testing/selftests/bpf/DENYLIST.aarch64
index e865451e90d2..2bf981c80180 100644
--- a/tools/testing/selftests/bpf/DENYLIST.aarch64
+++ b/tools/testing/selftests/bpf/DENYLIST.aarch64
@@ -1,6 +1,5 @@
bpf_cookie/multi_kprobe_attach_api # kprobe_multi_link_api_subtest:FAIL:fentry_raw_skel_load unexpected error: -3
bpf_cookie/multi_kprobe_link_api # kprobe_multi_link_api_subtest:FAIL:fentry_raw_skel_load unexpected error: -3
-fexit_sleep # The test never returns. The remaining tests cannot start.
kprobe_multi_bench_attach # needs CONFIG_FPROBE
kprobe_multi_test # needs CONFIG_FPROBE
module_attach # prog 'kprobe_multi': failed to auto-attach: -95
--
2.40.1
next reply other threads:[~2024-07-05 14:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 14:50 Puranjay Mohan [this message]
2024-07-08 14:52 ` [PATCH bpf] selftests/bpf: DENYLIST.aarch64: Remove fexit_sleep Daniel Borkmann
2024-07-08 15:00 ` Puranjay Mohan
2024-07-08 15:26 ` KP Singh
2024-07-08 15:29 ` Daniel Borkmann
2024-07-08 15:31 ` Florent Revest
2024-07-08 15:35 ` Puranjay Mohan
2024-07-08 16:09 ` Daniel Borkmann
2024-07-08 16:42 ` KP Singh
2024-07-09 17:44 ` Daniel Borkmann
2024-07-09 19:06 ` Manu Bretelle
2024-07-10 7:18 ` Puranjay Mohan
2024-07-11 14:00 ` Puranjay Mohan
2024-07-11 15:55 ` Daniel Borkmann
2024-07-12 13:50 ` Daniel Borkmann
2024-07-12 16:07 ` Alexei Starovoitov
2024-07-12 16:19 ` Daniel Borkmann
2024-07-15 16:31 ` Puranjay Mohan
2024-07-15 17:07 ` Alexei Starovoitov
2024-07-15 17:32 ` Puranjay Mohan
2024-07-12 17:27 ` Manu Bretelle
2024-07-12 18:08 ` Puranjay Mohan
2024-07-12 19:59 ` Manu Bretelle
2024-07-08 20:30 ` 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=20240705145009.32340-1-puranjay@kernel.org \
--to=puranjay@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=puranjay12@gmail.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--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