From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH bpf-next v3 0/6] core_reloc fixes for s390
Date: Mon, 25 Oct 2021 20:40:23 -0700 [thread overview]
Message-ID: <CAEf4BzbVLEyMmpk04YY20crwp5oj5Byi2_9zZAQ5AyNyejNe7Q@mail.gmail.com> (raw)
In-Reply-To: <20211026010831.748682-1-iii@linux.ibm.com>
On Mon, Oct 25, 2021 at 6:08 PM Ilya Leoshkevich <iii@linux.ibm.com> wrote:
>
> v2: https://lore.kernel.org/bpf/20211025131214.731972-1-iii@linux.ibm.com/
> v2 -> v3: Split the fix from the cleanup (Daniel).
>
> v1: https://lore.kernel.org/bpf/20211021234653.643302-1-iii@linux.ibm.com/
> v1 -> v2: Drop bpf_core_calc_field_relo() restructuring, split the
> __BYTE_ORDER__ change (Andrii).
>
> Hi,
>
> this series fixes test failures in core_reloc on s390.
>
> Patch 1 fixes an endianness bug with __BYTE_ORDER vs __BYTE_ORDER__.
> Patches 2-5 make the rest of the code consistent in that respect.
> Patch 6 fixes an endianness issue in test_core_reloc_mods.
>
Applied to bpf-next, thanks.
> Best regards,
> Ilya
>
> Ilya Leoshkevich (6):
> libbpf: Fix endianness detection in BPF_CORE_READ_BITFIELD_PROBED()
> libbpf: Use __BYTE_ORDER__
> selftests/bpf: Use __BYTE_ORDER__
> samples: seccomp: use __BYTE_ORDER__
> selftests/seccomp: Use __BYTE_ORDER__
> selftests/bpf: Fix test_core_reloc_mods on big-endian machines
>
> samples/seccomp/bpf-helper.h | 8 ++++----
> tools/lib/bpf/bpf_core_read.h | 2 +-
> tools/lib/bpf/btf.c | 4 ++--
> tools/lib/bpf/btf_dump.c | 8 ++++----
> tools/lib/bpf/libbpf.c | 4 ++--
> tools/lib/bpf/linker.c | 12 ++++++------
> tools/lib/bpf/relo_core.c | 2 +-
> .../testing/selftests/bpf/prog_tests/btf_endian.c | 6 +++---
> .../selftests/bpf/progs/test_core_reloc_mods.c | 9 +++++++++
> tools/testing/selftests/bpf/test_sysctl.c | 4 ++--
> tools/testing/selftests/bpf/verifier/ctx_skb.c | 14 +++++++-------
> tools/testing/selftests/bpf/verifier/lwt.c | 2 +-
> .../bpf/verifier/perf_event_sample_period.c | 6 +++---
> tools/testing/selftests/seccomp/seccomp_bpf.c | 6 +++---
> 14 files changed, 48 insertions(+), 39 deletions(-)
>
> --
> 2.31.1
>
prev parent reply other threads:[~2021-10-26 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 1:08 [PATCH bpf-next v3 0/6] core_reloc fixes for s390 Ilya Leoshkevich
2021-10-26 1:08 ` [PATCH bpf-next v3 1/6] libbpf: Fix endianness detection in BPF_CORE_READ_BITFIELD_PROBED() Ilya Leoshkevich
2021-10-26 1:08 ` [PATCH bpf-next v3 2/6] libbpf: Use __BYTE_ORDER__ Ilya Leoshkevich
2021-10-27 19:05 ` Arnaldo Carvalho de Melo
2021-10-26 1:08 ` [PATCH bpf-next v3 3/6] selftests/bpf: " Ilya Leoshkevich
2021-10-26 1:08 ` [PATCH bpf-next v3 4/6] samples: seccomp: use __BYTE_ORDER__ Ilya Leoshkevich
2021-10-26 1:08 ` [PATCH bpf-next v3 5/6] selftests/seccomp: Use __BYTE_ORDER__ Ilya Leoshkevich
2021-10-26 1:08 ` [PATCH bpf-next v3 6/6] selftests/bpf: Fix test_core_reloc_mods on big-endian machines Ilya Leoshkevich
2021-10-26 3:40 ` Andrii Nakryiko [this message]
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=CAEf4BzbVLEyMmpk04YY20crwp5oj5Byi2_9zZAQ5AyNyejNe7Q@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.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;
as well as URLs for NNTP newsgroup(s).