From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Hari Bathini <hbathini@linux.ibm.com>
Cc: Yonghong Song <yonghong.song@linux.dev>,
bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Shuah Khan <shuah@kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH bpf-next v2] selftests/bpf: improve test coverage for kfunc call
Date: Fri, 13 Mar 2026 17:51:46 +0100 [thread overview]
Message-ID: <86ea999a-12a9-426a-ab8b-abfc5efa8de4@linux.ibm.com> (raw)
In-Reply-To: <CAADnVQK--hKVH=FBMLiF7io2kBLfqwkXM9porBS1T--og=R4Yw@mail.gmail.com>
On 3/13/26 15:20, Alexei Starovoitov wrote:
[...]
> I was about to apply it, but it fails on s390. See CI:
>
> Error: #160 kfunc_call
> Error: #160/13 kfunc_call/kfunc_call_test5_asm
> Error: #160/13 kfunc_call/kfunc_call_test5_asm
> verify_success:PASS:skel 0 nsec
> verify_success:PASS:bpf_object__find_program_by_name 0 nsec
> verify_success:PASS:kfunc_call_test5_asm 0 nsec
> verify_success:FAIL:retval unexpected retval: actual 6 != expected 0
> Test Results:
> bpftool: PASS
> test_progs: FAIL (returned 1)
>
> It doesn't look to be endianness related (which is often
> the case for breaking s390).
> In this case it could be an s390 JIT issue?
>
> Ilya ?
>
> pw-bot: cr
I implemented sign-extension required by the s390x ABI, but forgot about
zero-extension.
I will send the fix soon, after ./test_progs completes.
next prev parent reply other threads:[~2026-03-13 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 8:01 [PATCH bpf-next v2] selftests/bpf: improve test coverage for kfunc call Hari Bathini
2026-03-12 18:22 ` Yonghong Song
2026-03-13 9:29 ` Hari Bathini
2026-03-13 14:20 ` Alexei Starovoitov
2026-03-13 16:51 ` Ilya Leoshkevich [this message]
2026-03-13 16:22 ` Mykyta Yatsenko
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=86ea999a-12a9-426a-ab8b-abfc5efa8de4@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hbathini@linux.ibm.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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