From: "Ihor Solodrai" <ihor.solodrai@linux.dev>
To: "Ilya Leoshkevich" <iii@linux.ibm.com>
Cc: "Yonghong Song" <yonghong.song@linux.dev>,
"Song Liu" <song@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
bpf@vger.kernel.org, kernel-team@meta.com
Subject: s390x: selftests/bpf are failing on CI
Date: Mon, 31 Mar 2025 18:25:35 +0000 [thread overview]
Message-ID: <7adb418e282468fcd5dc10c05790614e622579d4@linux.dev> (raw)
Hi Ilya,
After recent merges from upstream, CI started failing both on bpf and
bpf-next trees. Yonghong Song and Song Liu submitted a couple of fixes
that are already applied to bpf tree, but there are still failures on
s390x.
https://github.com/kernel-patches/bpf/actions/runs/14163772245
Could you please investigate?
A snippet from the log:
#11 atomics:OK
trace_kprobe: Could not probe notrace function __s390x_sys_bpf
trace_kprobe: Could not probe notrace function __s390x_sys_nanosleep
trace_kprobe: Could not probe notrace function __s390x_sys_nanosleep
trace_kprobe: Could not probe notrace function __s390x_sys_nanosleep
trace_kprobe: Could not probe notrace function __s390x_sys_nanosleep
trace_kprobe: Could not probe notrace function __s390x_sys_nanosleep
test_attach_probe:PASS:skel_open 0 nsec
test_attach_probe:PASS:skel_load 0 nsec
test_attach_probe:PASS:check_bss 0 nsec
test_attach_probe_manual:PASS:skel_kprobe_manual_open_and_load 0 nsec
test_attach_probe_manual:PASS:uprobe_offset 0 nsec
libbpf: prog 'handle_kprobe': failed to create kprobe '__s390x_sys_nanosleep+0x0' perf event: -EINVAL
test_attach_probe_manual:FAIL:attach_kprobe unexpected error: -22
#12/1 attach_probe/manual-default:FAIL
test_attach_probe_manual:PASS:skel_kprobe_manual_open_and_load 0 nsec
test_attach_probe_manual:PASS:uprobe_offset 0 nsec
libbpf: failed to add legacy kprobe event for '__s390x_sys_nanosleep+0x0': -EINVAL
libbpf: prog 'handle_kprobe': failed to create kprobe '__s390x_sys_nanosleep+0x0' perf event: -EINVAL
test_attach_probe_manual:FAIL:attach_kprobe unexpected error: -22
#12/2 attach_probe/manual-legacy:FAIL
test_attach_probe_manual:PASS:skel_kprobe_manual_open_and_load 0 nsec
test_attach_probe_manual:PASS:uprobe_offset 0 nsec
libbpf: prog 'handle_kprobe': failed to create kprobe '__s390x_sys_nanosleep+0x0' perf event: -EINVAL
test_attach_probe_manual:FAIL:attach_kprobe unexpected error: -22
#12/3 attach_probe/manual-perf:FAIL
test_attach_probe_manual:PASS:skel_kprobe_manual_open_and_load 0 nsec
test_attach_probe_manual:PASS:uprobe_offset 0 nsec
libbpf: prog 'handle_kprobe': failed to create kprobe '__s390x_sys_nanosleep+0x0' perf event: -EINVAL
test_attach_probe_manual:FAIL:attach_kprobe unexpected error: -22
#12/4 attach_probe/manual-link:FAIL
libbpf: prog 'handle_kprobe_auto': failed to create kprobe '__se_sys_nanosleep+0x0' perf event: -ENOENT
test_attach_probe_auto:FAIL:attach_kprobe_auto unexpected error: -2
libbpf: prog 'handle_kretprobe_auto': failed to create kretprobe '__se_sys_nanosleep+0x0' perf event: -ENOENT
test_attach_probe_auto:FAIL:attach_kretprobe_auto unexpected error: -2
test_attach_probe_auto:PASS:auto-attach should fail for old-style name 0 nsec
test_attach_probe_auto:PASS:attach_uretprobe_byname 0 nsec
test_attach_probe_auto:FAIL:check_kprobe_auto_res unexpected check_kprobe_auto_res: actual 0 != expected 11
test_attach_probe_auto:FAIL:check_kretprobe_auto_res unexpected check_kretprobe_auto_res: actual 0 != expected 22
test_attach_probe_auto:PASS:check_uretprobe_byname_res 0 nsec
#12/5 attach_probe/auto:FAIL
next reply other threads:[~2025-03-31 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 18:25 Ihor Solodrai [this message]
2025-03-31 22:45 ` s390x: selftests/bpf are failing on CI Ihor Solodrai
[not found] ` <1199a2932ed1800fa0a898e67ba74590@imap.linux.ibm.com>
[not found] ` <a1b5ac5e01e50a6f3dc1047a08b725d6@imap.linux.ibm.com>
2025-04-01 15:53 ` Vasily Gorbik
2025-04-01 18:14 ` Ihor Solodrai
2025-04-01 18:23 ` Ihor Solodrai
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=7adb418e282468fcd5dc10c05790614e622579d4@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=iii@linux.ibm.com \
--cc=kernel-team@meta.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