BPF List
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	bpf@vger.kernel.org, Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH bpf-next v2 0/2] Fix test_probe_user on s390x
Date: Tue, 26 Jul 2022 16:14:33 +0200	[thread overview]
Message-ID: <Yt/2yTe3CSKApQui@krava> (raw)
In-Reply-To: <20220726134008.256968-1-iii@linux.ibm.com>

On Tue, Jul 26, 2022 at 03:40:06PM +0200, Ilya Leoshkevich wrote:
> 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).

LGTM 

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

> 
> 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
> 

  parent reply	other threads:[~2022-07-26 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 13:40 [PATCH bpf-next v2 0/2] Fix test_probe_user on s390x Ilya Leoshkevich
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 ` Jiri Olsa [this message]
2022-07-26 14:37   ` [PATCH bpf-next v2 0/2] Fix test_probe_user on s390x 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=Yt/2yTe3CSKApQui@krava \
    --to=olsajiri@gmail.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=iii@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