Skip to content

Fix test_probe_user on s390x

Ilya Leoshkevich bpf 2 versions – Applied

Status from this message: Applied, thanks Ilya!

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest2 patches 2 repliesApplied
  2. v12 patches 2 repliesSuperseded

Patches in v2 Applied

#Subject and filesSizeRepliesApplied
1/2libbpf: Extend BPF_KSYSCALL documentationtools/lib/bpf/bpf_tracing.h+11 -40 replies
2/2selftests/bpf: Attach to socketcall() in test_probe_usertools/testing/selftests/bpf/prog_tests/probe_user.c tools/testing/selftests/bpf/progs/test_probe_user.c+54 -130 replies

Reviews trailers per patch

None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchJiri Olsa
SeriesA-b
1/2
2/2

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

Cover letter [PATCH bpf-next v2 0/2] Fix test_probe_user on s390x

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/[email protected]/

v1: https://lore.kernel.org/bpf/[email protected]/
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(-)
Signature · 1 line
2.35.3