From: Jiri Olsa <olsajiri@gmail.com>
To: Viktor Malik <vmalik@redhat.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Daniel Xu <dxu@dxuuu.xyz>, Manu Bretelle <chantr4@gmail.com>
Subject: Re: [PATCH bpf-next v4 0/2] tools/resolve_btfids: fix cross-compilation to non-host endianness
Date: Tue, 6 Feb 2024 15:57:25 +0100 [thread overview]
Message-ID: <ZcJI1auXFbrckOnz@krava> (raw)
In-Reply-To: <cover.1707223196.git.vmalik@redhat.com>
On Tue, Feb 06, 2024 at 01:46:08PM +0100, Viktor Malik wrote:
> The .BTF_ids section is pre-filled with zeroed BTF ID entries during the
> build and afterwards patched by resolve_btfids with correct values.
> Since resolve_btfids always writes in host-native endianness, it relies
> on libelf to do the translation when the target ELF is cross-compiled to
> a different endianness (this was introduced in commit 61e8aeda9398
> ("bpf: Fix libelf endian handling in resolv_btfids")).
>
> Unfortunately, the translation will corrupt the flags fields of SET8
> entries because these were written during vmlinux compilation and are in
> the correct endianness already. This will lead to numerous selftests
> failures such as:
>
> $ sudo ./test_verifier 502 502
> #502/p sleepable fentry accept FAIL
> Failed to load prog 'Invalid argument'!
> bpf_fentry_test1 is not sleepable
> verification time 34 usec
> stack depth 0
> processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
> Summary: 0 PASSED, 0 SKIPPED, 1 FAILED
>
> Since it's not possible to instruct libelf to translate just certain
> values, let's manually bswap the flags (both global and entry flags) in
> resolve_btfids when needed, so that libelf then translates everything
> correctly.
>
> The first patch of the series refactors resolve_btfids by using types
> from btf_ids.h instead of accessing the BTF ID data using magic offsets.
>
> ---
> Changes in v4:
> - remove unnecessary vars and pointer casts (suggested by Daniel Xu)
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
>
> Changes in v3:
> - add byte swap of global 'flags' field in btf_id_set8 (suggested by
> Jiri Olsa)
> - cleaner refactoring of sets_patch (suggested by Jiri Olsa)
> - add compile-time assertion that IDs are at the beginning of pairs
> struct in btf_id_set8 (suggested by Daniel Borkmann)
>
> Changes in v2:
> - use type defs from btf_ids.h (suggested by Andrii Nakryiko)
>
> Viktor Malik (2):
> tools/resolve_btfids: Refactor set sorting with types from btf_ids.h
> tools/resolve_btfids: fix cross-compilation to non-host endianness
>
> tools/bpf/resolve_btfids/main.c | 70 ++++++++++++++++++++++++++-------
> tools/include/linux/btf_ids.h | 9 +++++
> 2 files changed, 65 insertions(+), 14 deletions(-)
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-02-06 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 12:46 [PATCH bpf-next v4 0/2] tools/resolve_btfids: fix cross-compilation to non-host endianness Viktor Malik
2024-02-06 12:46 ` [PATCH bpf-next v4 1/2] tools/resolve_btfids: Refactor set sorting with types from btf_ids.h Viktor Malik
2024-02-06 15:28 ` Daniel Xu
2024-02-06 12:46 ` [PATCH bpf-next v4 2/2] tools/resolve_btfids: fix cross-compilation to non-host endianness Viktor Malik
2024-02-06 14:57 ` Jiri Olsa [this message]
2024-02-08 0:20 ` [PATCH bpf-next v4 0/2] " patchwork-bot+netdevbpf
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=ZcJI1auXFbrckOnz@krava \
--to=olsajiri@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chantr4@gmail.com \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=vmalik@redhat.com \
--cc=yonghong.song@linux.dev \
/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