libbpf: fix cross-endian build with newer libbpf
Subsystems (2)
PATCH v2 1/1 libbpf: fix cross-endian build with newer libbpf
commit 087f3964f4b3 ("libbpf: Support layout section handling in BTF") added extra data to the BTF header.
This extra data is ignored in the native case, but when building with different endianness the bswap code in old libbpf would check for strict size equality, leading to build failures such as this when BTF data is generated with a newer version of libbpf (through pahole)
BTFIDS vmlinux.unstripped
libbpf: Can't load BTF with non-native endianness due to unsupported header length 32
FAILED: load BTF from vmlinux.unstripped: Operation not supported make[2]: *** [../scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 255
Newer libbpf versions also properly ignore trailing data in the bswap case, but the patch is too intrusive to backport, so take the header length comparison fix from it instead.
---
v1 -> v2:
- link to v1: https://lore.kernel.org/r/[email protected]
- use offsetofend() instead of sizeof() to match the support layout section handling patch as suggested by Alan
I checked this builds on 5.10 (non-cross-endian build) and 6.18 (ppc64 cross build)
- add Fixes tag as suggested by sashiko
tools/lib/bpf/btf.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/lib/bpf/btf.c +2 -2
@@ -229,14 +229,14 @@ static int btf_parse_hdr(struct btf *btf)struct btf_header *hdr = btf->hdr;__u32 meta_left; -if (btf->raw_size <sizeof (struct btf_header )) { + if (btf->raw_size < offsetofend(struct btf_header, str_len)) {pr_debug ("BTF header not found\n" );return -EINVAL ; }if (hdr->magic ==bswap_16 (BTF_MAGIC )) { btf->swapped_endian = true; -if (bswap_32 (hdr->hdr_len) !=sizeof (struct btf_header )) { + if (bswap_32(hdr->hdr_len) < offsetofend(struct btf_header, str_len)) {pr_warn ("Can't load BTF with non-native endianness due to unsupported header length %u\n" ,bswap_32 (hdr->hdr_len));return -ENOTSUP ;
Signature · 1 line
2.56.1
Greg KH
maintainerQuoted 56 lines · Dominique Martinet
commit
087f3964f4b3("libbpf: Support layout section handling in BTF") added extra data to the BTF header.This extra data is ignored in the native case, but when building with different endianness the bswap code in old libbpf would check for strict size equality, leading to build failures such as this when BTF data is generated with a newer version of libbpf (through pahole)
BTFIDS vmlinux.unstripped
libbpf: Can't load BTF with non-native endianness due to unsupported header length 32
FAILED: load BTF from vmlinux.unstripped: Operation not supported make[2]: *** [../scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 255Newer libbpf versions also properly ignore trailing data in the bswap case, but the patch is too intrusive to backport, so take the header length comparison fix from it instead.
Fixes 3289959b97ca ("libbpf: Support BTF loading and raw data output in both endianness")Acked-by Alan Maguire <[email protected]>Signed-off-by Dominique Martinet <[email protected]>---
v1 -> v2:
- link to v1: https://lore.kernel.org/r/[email protected]
- useoffsetofend()instead ofsizeof()to match the support layout section handling patch as suggested by Alan
I checked this builds on 5.10 (non-cross-endian build) and 6.18 (ppc64 cross build)
- add Fixes tag as suggested by sashikotools/lib/bpf/btf.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)tools/lib/bpf/btf.c +2
-2@@ -229,14 +229,14 @@ static int btf_parse_hdr(struct btf *btf)struct btf_header *hdr = btf->hdr;__u32 meta_left; -if (btf->raw_size <sizeof (struct btf_header )) { + if (btf->raw_size < offsetofend(struct btf_header, str_len)) {pr_debug ("BTF header not found\n" );return -EINVAL ; }if (hdr->magic ==bswap_16 (BTF_MAGIC )) { btf->swapped_endian = true; -if (bswap_32 (hdr->hdr_len) !=sizeof (struct btf_header )) { + if (bswap_32(hdr->hdr_len) < offsetofend(struct btf_header, str_len)) {pr_warn ("Can't load BTF with non-native endianness due to unsupported header length %u\n" ,bswap_32 (hdr->hdr_len));return -ENOTSUP ;Signature · 1 line
2.56.1
<formletter>
This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
Quoted 3 lines
Newer libbpf versions also properly ignore trailing data in the bswap case, but the patch is too intrusive to backport, so take the header length comparison fix from it instead.
Queued for 6.18, 6.12, 6.6, 6.1, 5.15 and 5.10, thanks.
Signature · 2 lines
Thanks, Sasha