From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Cc: bpf@vger.kernel.org, Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH bpf-next 0/3] libbpf: Fix accessing the first syscall argument on s390
Date: Wed, 2 Feb 2022 00:41:57 +0100 [thread overview]
Message-ID: <20220201234200.1836443-1-iii@linux.ibm.com> (raw)
libbpf CI reported a bpf_syscall_macro test failure on s390 [1], which
happens because the code uses gprs[2] instead of orig_gpr2 to access
the first syscall argument. Patches 1-2 are preparations, patch 3 fixes
the issue.
@Heiko, @Vasily, @Christian, @Alexander - could you please review
patch 1, which touches arch/s390? Would it be ok to put it into
bpf-next tree?
[1] https://github.com/libbpf/libbpf/runs/5025905587
Ilya Leoshkevich (3):
s390/bpf: Add orig_gpr2 to user_pt_regs
selftests/bpf: Fix an endianness issue in bpf_syscall_macro test
libbpf: Fix accessing the first syscall argument on s390
arch/s390/include/asm/ptrace.h | 2 +-
arch/s390/include/uapi/asm/ptrace.h | 1 +
tools/lib/bpf/bpf_tracing.h | 9 +++++++++
tools/testing/selftests/bpf/progs/bpf_syscall_macro.c | 5 ++++-
4 files changed, 15 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-01 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 23:41 Ilya Leoshkevich [this message]
2022-02-01 23:41 ` [PATCH bpf-next 1/3] s390/bpf: Add orig_gpr2 to user_pt_regs Ilya Leoshkevich
2022-02-02 14:19 ` Vasily Gorbik
2022-02-02 17:23 ` Christian Borntraeger
2022-02-03 9:40 ` Heiko Carstens
2022-02-02 20:14 ` Heiko Carstens
2022-02-02 22:49 ` Andrii Nakryiko
2022-02-04 6:07 ` Naveen N. Rao
2022-02-04 8:21 ` Naveen N. Rao
2022-02-04 12:20 ` Ilya Leoshkevich
2022-02-04 13:49 ` Naveen N. Rao
2022-02-01 23:41 ` [PATCH bpf-next 2/3] selftests/bpf: Fix an endianness issue in bpf_syscall_macro test Ilya Leoshkevich
2022-02-01 23:42 ` [PATCH bpf-next 3/3] libbpf: Fix accessing the first syscall argument on s390 Ilya Leoshkevich
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=20220201234200.1836443-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=borntraeger@linux.ibm.com \
--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