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 <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>, Jiri Olsa <jolsa@kernel.org>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH bpf-next v2 0/2] Fix test_probe_user on s390x
Date: Tue, 26 Jul 2022 15:40:06 +0200 [thread overview]
Message-ID: <20220726134008.256968-1-iii@linux.ibm.com> (raw)
Hi,
This is a fix for [1]: test_probe_user fails on s390x, because it hooks
only connect(), but not socketcall(SYS_CONNECT).
Patch 1 adds this quirk to BPF_KSYSCALL documentation.
Patch 2 fixes the test by attaching a prog to socketcall().
Best regards,
Ilya
[1] https://lore.kernel.org/bpf/06631b122b9bd6258139a36b971bba3e79543503.camel@linux.ibm.com/
v1: https://lore.kernel.org/bpf/20220723020344.21699-1-iii@linux.ibm.com/
v1 -> v2: Add CONFIG_ prefix to CLONE_BACKWARDS* symbols (Jiri).
Change the type of prog_names to make checkpatch happy.
Use prog_count everywhere (Jiri).
#ifdef out handle_sys_socketcall() on non-s390x (Jiri).
Ilya Leoshkevich (2):
libbpf: Extend BPF_KSYSCALL documentation
selftests/bpf: Attach to socketcall() in test_probe_user
tools/lib/bpf/bpf_tracing.h | 15 +++++---
.../selftests/bpf/prog_tests/probe_user.c | 35 +++++++++++++------
.../selftests/bpf/progs/test_probe_user.c | 32 +++++++++++++++--
3 files changed, 65 insertions(+), 17 deletions(-)
--
2.35.3
next reply other threads:[~2022-07-26 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 13:40 Ilya Leoshkevich [this message]
2022-07-26 13:40 ` [PATCH bpf-next v2 1/2] libbpf: Extend BPF_KSYSCALL documentation Ilya Leoshkevich
2022-07-26 13:40 ` [PATCH bpf-next v2 2/2] selftests/bpf: Attach to socketcall() in test_probe_user Ilya Leoshkevich
2022-07-26 14:14 ` [PATCH bpf-next v2 0/2] Fix test_probe_user on s390x Jiri Olsa
2022-07-26 14:37 ` Daniel Borkmann
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=20220726134008.256968-1-iii@linux.ibm.com \
--to=iii@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=heiko.carstens@de.ibm.com \
--cc=jolsa@kernel.org \
/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