diff mbox series

[bpf-next] tools/resolve_btfids: fix cross-compilation to non-host endianness

Message ID 20240123120759.1865189-1-vmalik@redhat.com (mailing list archive)
State Superseded
Delegated to: BPF
Headers show
Series [bpf-next] tools/resolve_btfids: fix cross-compilation to non-host endianness | expand

Checks

Context Check Description
netdev/series_format success Single patches do not need cover letters
netdev/tree_selection success Clearly marked for bpf-next
netdev/ynl success SINGLE THREAD; Generated files up to date; no warnings/errors; no diff in generated;
netdev/fixes_present success Fixes tag not required for -next series
netdev/header_inline success No static functions without inline keyword in header files
netdev/build_32bit success Errors and warnings before: 8 this patch: 8
netdev/build_tools success Errors and warnings before: 1 this patch: 0
netdev/cc_maintainers success CCed 0 of 0 maintainers
netdev/build_clang success Errors and warnings before: 8 this patch: 8
netdev/verify_signedoff success Signed-off-by tag matches author and committer
netdev/deprecated_api success None detected
netdev/check_selftest success No net selftest shell script
netdev/verify_fixes success Fixes tag looks correct
netdev/build_allmodconfig_warn success Errors and warnings before: 8 this patch: 8
netdev/checkpatch warning CHECK: Alignment should match open parenthesis CHECK: Comparison to NULL could be written "!gelf_getehdr" WARNING: Comparisons should place the constant on the right side of the test WARNING: line length of 82 exceeds 80 columns
netdev/build_clang_rust success No Rust files in patch. Skipping build
netdev/kdoc success Errors and warnings before: 0 this patch: 0
netdev/source_inline success Was 0 now: 0
bpf/vmtest-bpf-next-PR success PR summary
bpf/vmtest-bpf-next-VM_Test-16 success Logs for s390x-gcc / test (test_verifier, false, 360) / test_verifier on s390x with gcc
bpf/vmtest-bpf-next-VM_Test-0 success Logs for Lint
bpf/vmtest-bpf-next-VM_Test-2 success Logs for Unittests
bpf/vmtest-bpf-next-VM_Test-5 success Logs for aarch64-gcc / build-release
bpf/vmtest-bpf-next-VM_Test-1 success Logs for ShellCheck
bpf/vmtest-bpf-next-VM_Test-3 success Logs for Validate matrix.py
bpf/vmtest-bpf-next-VM_Test-12 success Logs for s390x-gcc / build-release
bpf/vmtest-bpf-next-VM_Test-4 success Logs for aarch64-gcc / build / build for aarch64 with gcc
bpf/vmtest-bpf-next-VM_Test-10 success Logs for aarch64-gcc / veristat
bpf/vmtest-bpf-next-VM_Test-9 success Logs for aarch64-gcc / test (test_verifier, false, 360) / test_verifier on aarch64 with gcc
bpf/vmtest-bpf-next-VM_Test-15 success Logs for x86_64-gcc / build-release
bpf/vmtest-bpf-next-VM_Test-6 success Logs for aarch64-gcc / test (test_maps, false, 360) / test_maps on aarch64 with gcc
bpf/vmtest-bpf-next-VM_Test-14 success Logs for x86_64-gcc / build / build for x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-13 success Logs for set-matrix
bpf/vmtest-bpf-next-VM_Test-8 success Logs for aarch64-gcc / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on aarch64 with gcc
bpf/vmtest-bpf-next-VM_Test-11 success Logs for s390x-gcc / build / build for s390x with gcc
bpf/vmtest-bpf-next-VM_Test-17 success Logs for s390x-gcc / veristat
bpf/vmtest-bpf-next-VM_Test-7 fail Logs for aarch64-gcc / test (test_progs, false, 360) / test_progs on aarch64 with gcc
bpf/vmtest-bpf-next-VM_Test-28 success Logs for x86_64-llvm-17 / build / build for x86_64 with llvm-17
bpf/vmtest-bpf-next-VM_Test-20 success Logs for x86_64-gcc / build-release
bpf/vmtest-bpf-next-VM_Test-36 success Logs for x86_64-llvm-18 / build-release / build for x86_64 with llvm-18 and -O2 optimization
bpf/vmtest-bpf-next-VM_Test-19 success Logs for x86_64-gcc / build / build for x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-35 success Logs for x86_64-llvm-18 / build / build for x86_64 with llvm-18
bpf/vmtest-bpf-next-VM_Test-18 success Logs for set-matrix
bpf/vmtest-bpf-next-VM_Test-34 success Logs for x86_64-llvm-17 / veristat
bpf/vmtest-bpf-next-VM_Test-42 success Logs for x86_64-llvm-18 / veristat
bpf/vmtest-bpf-next-VM_Test-25 success Logs for x86_64-gcc / test (test_progs_parallel, true, 30) / test_progs_parallel on x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-32 success Logs for x86_64-llvm-17 / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on x86_64 with llvm-17
bpf/vmtest-bpf-next-VM_Test-31 success Logs for x86_64-llvm-17 / test (test_progs, false, 360) / test_progs on x86_64 with llvm-17
bpf/vmtest-bpf-next-VM_Test-21 success Logs for x86_64-gcc / test (test_maps, false, 360) / test_maps on x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-22 success Logs for x86_64-gcc / test (test_progs, false, 360) / test_progs on x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-26 success Logs for x86_64-gcc / test (test_verifier, false, 360) / test_verifier on x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-41 success Logs for x86_64-llvm-18 / test (test_verifier, false, 360) / test_verifier on x86_64 with llvm-18
bpf/vmtest-bpf-next-VM_Test-23 success Logs for x86_64-gcc / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-33 success Logs for x86_64-llvm-17 / test (test_verifier, false, 360) / test_verifier on x86_64 with llvm-17
bpf/vmtest-bpf-next-VM_Test-29 success Logs for x86_64-llvm-17 / build-release / build for x86_64 with llvm-17 and -O2 optimization
bpf/vmtest-bpf-next-VM_Test-24 success Logs for x86_64-gcc / test (test_progs_no_alu32_parallel, true, 30) / test_progs_no_alu32_parallel on x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-27 success Logs for x86_64-gcc / veristat / veristat on x86_64 with gcc
bpf/vmtest-bpf-next-VM_Test-30 success Logs for x86_64-llvm-17 / test (test_maps, false, 360) / test_maps on x86_64 with llvm-17
bpf/vmtest-bpf-next-VM_Test-37 success Logs for x86_64-llvm-18 / test (test_maps, false, 360) / test_maps on x86_64 with llvm-18
bpf/vmtest-bpf-next-VM_Test-39 success Logs for x86_64-llvm-18 / test (test_progs_cpuv4, false, 360) / test_progs_cpuv4 on x86_64 with llvm-18
bpf/vmtest-bpf-next-VM_Test-40 success Logs for x86_64-llvm-18 / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on x86_64 with llvm-18
bpf/vmtest-bpf-next-VM_Test-38 success Logs for x86_64-llvm-18 / test (test_progs, false, 360) / test_progs on x86_64 with llvm-18

Commit Message

Viktor Malik Jan. 23, 2024, 12:07 p.m. UTC
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 in resolve_btfids when needed, so
that libelf then translates everything correctly.

Fixes: ef2c6f370a63 ("tools/resolve_btfids: Add support for 8-byte BTF sets")
Signed-off-by: Viktor Malik <vmalik@redhat.com>
---
 tools/bpf/resolve_btfids/main.c | 35 +++++++++++++++++++++++++++++++--
 1 file changed, 33 insertions(+), 2 deletions(-)

Comments

Andrii Nakryiko Jan. 26, 2024, 11:40 p.m. UTC | #1
On Tue, Jan 23, 2024 at 4:08 AM Viktor Malik <vmalik@redhat.com> 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 in resolve_btfids when needed, so
> that libelf then translates everything correctly.
>
> Fixes: ef2c6f370a63 ("tools/resolve_btfids: Add support for 8-byte BTF sets")
> Signed-off-by: Viktor Malik <vmalik@redhat.com>
> ---
>  tools/bpf/resolve_btfids/main.c | 35 +++++++++++++++++++++++++++++++--
>  1 file changed, 33 insertions(+), 2 deletions(-)
>
> diff --git a/tools/bpf/resolve_btfids/main.c b/tools/bpf/resolve_btfids/main.c
> index 27a23196d58e..440d3d066ce4 100644
> --- a/tools/bpf/resolve_btfids/main.c
> +++ b/tools/bpf/resolve_btfids/main.c
> @@ -646,18 +646,31 @@ static int cmp_id(const void *pa, const void *pb)
>         return *a - *b;
>  }
>
> +static int need_bswap(int elf_byte_order)
> +{
> +       return __BYTE_ORDER == __LITTLE_ENDIAN && elf_byte_order != ELFDATA2LSB ||
> +              __BYTE_ORDER == __BIG_ENDIAN && elf_byte_order != ELFDATA2MSB;

return (__BYTE_ORDER == __LITTLE_ENDIAN) != (elf_byte_order == ELFDATA2LSB);

?

> +}
> +
>  static int sets_patch(struct object *obj)
>  {
>         Elf_Data *data = obj->efile.idlist;
>         int *ptr = data->d_buf;
>         struct rb_node *next;
> +       GElf_Ehdr ehdr;
> +
> +       if (gelf_getehdr(obj->efile.elf, &ehdr) == NULL) {
> +               pr_err("FAILED cannot get ELF header: %s\n",
> +                       elf_errmsg(-1));
> +               return -1;
> +       }

calculate needs_bswap() once here?

>
>         next = rb_first(&obj->sets);
>         while (next) {
> -               unsigned long addr, idx;
> +               unsigned long addr, idx, flags;
>                 struct btf_id *id;
>                 int *base;
> -               int cnt;
> +               int cnt, i;
>
>                 id   = rb_entry(next, struct btf_id, rb_node);
>                 addr = id->addr[0];
> @@ -679,6 +692,24 @@ static int sets_patch(struct object *obj)
>
>                 qsort(base, cnt, id->is_set8 ? sizeof(uint64_t) : sizeof(int), cmp_id);
>
> +               /*
> +                * When ELF endianness does not match endianness of the host,
> +                * libelf will do the translation when updating the ELF. This,
> +                * however, corrupts SET8 flags which are already in the target
> +                * endianness. So, let's bswap them to the host endianness and
> +                * libelf will then correctly translate everything.
> +                */
> +               if (id->is_set8 && need_bswap(ehdr.e_ident[EI_DATA])) {
> +                       for (i = 0; i < cnt; i++) {
> +                               /*
> +                                * header and entries are 8-byte, flags is the
> +                                * second half of an entry
> +                                */
> +                               flags = idx + (i + 1) * 2 + 1;
> +                               ptr[flags] = bswap_32(ptr[flags]);

we are dealing with struct btf_id_set8, right? Can't we #include
include/linux/btf_ids.h and use that type for all these offset
calculations?..

I have the same question for existing code, tbh, so maybe there was
some good reason, not sure...

> +                       }
> +               }
> +
>                 next = rb_next(next);
>         }
>         return 0;
> --
> 2.43.0
>
>
Jiri Olsa Jan. 28, 2024, 8:17 p.m. UTC | #2
On Fri, Jan 26, 2024 at 03:40:11PM -0800, Andrii Nakryiko wrote:
> On Tue, Jan 23, 2024 at 4:08 AM Viktor Malik <vmalik@redhat.com> 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

hum, I'd think we should have hit such bug long time ago.. set8 is
there for some time already.. nice ;-)

> >
> > Since it's not possible to instruct libelf to translate just certain
> > values, let's manually bswap the flags in resolve_btfids when needed, so
> > that libelf then translates everything correctly.
> >
> > Fixes: ef2c6f370a63 ("tools/resolve_btfids: Add support for 8-byte BTF sets")
> > Signed-off-by: Viktor Malik <vmalik@redhat.com>
> > ---
> >  tools/bpf/resolve_btfids/main.c | 35 +++++++++++++++++++++++++++++++--
> >  1 file changed, 33 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/bpf/resolve_btfids/main.c b/tools/bpf/resolve_btfids/main.c
> > index 27a23196d58e..440d3d066ce4 100644
> > --- a/tools/bpf/resolve_btfids/main.c
> > +++ b/tools/bpf/resolve_btfids/main.c
> > @@ -646,18 +646,31 @@ static int cmp_id(const void *pa, const void *pb)
> >         return *a - *b;
> >  }
> >
> > +static int need_bswap(int elf_byte_order)
> > +{
> > +       return __BYTE_ORDER == __LITTLE_ENDIAN && elf_byte_order != ELFDATA2LSB ||
> > +              __BYTE_ORDER == __BIG_ENDIAN && elf_byte_order != ELFDATA2MSB;
> 
> return (__BYTE_ORDER == __LITTLE_ENDIAN) != (elf_byte_order == ELFDATA2LSB);
> 
> ?
> 
> > +}
> > +
> >  static int sets_patch(struct object *obj)
> >  {
> >         Elf_Data *data = obj->efile.idlist;
> >         int *ptr = data->d_buf;
> >         struct rb_node *next;
> > +       GElf_Ehdr ehdr;
> > +
> > +       if (gelf_getehdr(obj->efile.elf, &ehdr) == NULL) {
> > +               pr_err("FAILED cannot get ELF header: %s\n",
> > +                       elf_errmsg(-1));
> > +               return -1;
> > +       }
> 
> calculate needs_bswap() once here?
> 
> >
> >         next = rb_first(&obj->sets);
> >         while (next) {
> > -               unsigned long addr, idx;
> > +               unsigned long addr, idx, flags;
> >                 struct btf_id *id;
> >                 int *base;
> > -               int cnt;
> > +               int cnt, i;
> >
> >                 id   = rb_entry(next, struct btf_id, rb_node);
> >                 addr = id->addr[0];
> > @@ -679,6 +692,24 @@ static int sets_patch(struct object *obj)
> >
> >                 qsort(base, cnt, id->is_set8 ? sizeof(uint64_t) : sizeof(int), cmp_id);
> >
> > +               /*
> > +                * When ELF endianness does not match endianness of the host,
> > +                * libelf will do the translation when updating the ELF. This,
> > +                * however, corrupts SET8 flags which are already in the target
> > +                * endianness. So, let's bswap them to the host endianness and
> > +                * libelf will then correctly translate everything.
> > +                */
> > +               if (id->is_set8 && need_bswap(ehdr.e_ident[EI_DATA])) {
> > +                       for (i = 0; i < cnt; i++) {
> > +                               /*
> > +                                * header and entries are 8-byte, flags is the
> > +                                * second half of an entry
> > +                                */
> > +                               flags = idx + (i + 1) * 2 + 1;
> > +                               ptr[flags] = bswap_32(ptr[flags]);
> 
> we are dealing with struct btf_id_set8, right? Can't we #include
> include/linux/btf_ids.h and use that type for all these offset
> calculations?..

we could, there's tools/include/linux/btf_ids.h, which we could include
in here, we do that in selftests.. but it needs to be updated with latest
kernel updates (at least with set8 struct)

> 
> I have the same question for existing code, tbh, so maybe there was
> some good reason, not sure...

I think the test came later and I did not think of it for the resolve_btfids
itself, I guess it might make the code more readable

thanks,
jirka

> 
> > +                       }
> > +               }
> > +
> >                 next = rb_next(next);
> >         }
> >         return 0;
> > --
> > 2.43.0
> >
> >
Viktor Malik Jan. 29, 2024, 10:09 a.m. UTC | #3
On 1/28/24 21:17, Jiri Olsa wrote:
> On Fri, Jan 26, 2024 at 03:40:11PM -0800, Andrii Nakryiko wrote:
>> On Tue, Jan 23, 2024 at 4:08 AM Viktor Malik <vmalik@redhat.com> 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
> 
> hum, I'd think we should have hit such bug long time ago.. set8 is
> there for some time already.. nice ;-)
> 
>>>
>>> Since it's not possible to instruct libelf to translate just certain
>>> values, let's manually bswap the flags in resolve_btfids when needed, so
>>> that libelf then translates everything correctly.
>>>
>>> Fixes: ef2c6f370a63 ("tools/resolve_btfids: Add support for 8-byte BTF sets")
>>> Signed-off-by: Viktor Malik <vmalik@redhat.com>
>>> ---
>>>  tools/bpf/resolve_btfids/main.c | 35 +++++++++++++++++++++++++++++++--
>>>  1 file changed, 33 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/tools/bpf/resolve_btfids/main.c b/tools/bpf/resolve_btfids/main.c
>>> index 27a23196d58e..440d3d066ce4 100644
>>> --- a/tools/bpf/resolve_btfids/main.c
>>> +++ b/tools/bpf/resolve_btfids/main.c
>>> @@ -646,18 +646,31 @@ static int cmp_id(const void *pa, const void *pb)
>>>         return *a - *b;
>>>  }
>>>
>>> +static int need_bswap(int elf_byte_order)
>>> +{
>>> +       return __BYTE_ORDER == __LITTLE_ENDIAN && elf_byte_order != ELFDATA2LSB ||
>>> +              __BYTE_ORDER == __BIG_ENDIAN && elf_byte_order != ELFDATA2MSB;
>>
>> return (__BYTE_ORDER == __LITTLE_ENDIAN) != (elf_byte_order == ELFDATA2LSB);
>>
>> ?
>>

It seemed to me a bit less readable this way, but sure, no problem with
this form either.

>>> +}
>>> +
>>>  static int sets_patch(struct object *obj)
>>>  {
>>>         Elf_Data *data = obj->efile.idlist;
>>>         int *ptr = data->d_buf;
>>>         struct rb_node *next;
>>> +       GElf_Ehdr ehdr;
>>> +
>>> +       if (gelf_getehdr(obj->efile.elf, &ehdr) == NULL) {
>>> +               pr_err("FAILED cannot get ELF header: %s\n",
>>> +                       elf_errmsg(-1));
>>> +               return -1;
>>> +       }
>>
>> calculate needs_bswap() once here?

Good idea, will do.

>>>
>>>         next = rb_first(&obj->sets);
>>>         while (next) {
>>> -               unsigned long addr, idx;
>>> +               unsigned long addr, idx, flags;
>>>                 struct btf_id *id;
>>>                 int *base;
>>> -               int cnt;
>>> +               int cnt, i;
>>>
>>>                 id   = rb_entry(next, struct btf_id, rb_node);
>>>                 addr = id->addr[0];
>>> @@ -679,6 +692,24 @@ static int sets_patch(struct object *obj)
>>>
>>>                 qsort(base, cnt, id->is_set8 ? sizeof(uint64_t) : sizeof(int), cmp_id);
>>>
>>> +               /*
>>> +                * When ELF endianness does not match endianness of the host,
>>> +                * libelf will do the translation when updating the ELF. This,
>>> +                * however, corrupts SET8 flags which are already in the target
>>> +                * endianness. So, let's bswap them to the host endianness and
>>> +                * libelf will then correctly translate everything.
>>> +                */
>>> +               if (id->is_set8 && need_bswap(ehdr.e_ident[EI_DATA])) {
>>> +                       for (i = 0; i < cnt; i++) {
>>> +                               /*
>>> +                                * header and entries are 8-byte, flags is the
>>> +                                * second half of an entry
>>> +                                */
>>> +                               flags = idx + (i + 1) * 2 + 1;
>>> +                               ptr[flags] = bswap_32(ptr[flags]);
>>
>> we are dealing with struct btf_id_set8, right? Can't we #include
>> include/linux/btf_ids.h and use that type for all these offset
>> calculations?..
> 
> we could, there's tools/include/linux/btf_ids.h, which we could include
> in here, we do that in selftests.. but it needs to be updated with latest
> kernel updates (at least with set8 struct)
> 
>>
>> I have the same question for existing code, tbh, so maybe there was
>> some good reason, not sure...
> 
> I think the test came later and I did not think of it for the resolve_btfids
> itself, I guess it might make the code more readable

Agreed, let's use that. I'll also refactor the existing code using types
from btf_ids.h for v2 of this patchset.

Viktor

> 
> thanks,
> jirka
> 
>>
>>> +                       }
>>> +               }
>>> +
>>>                 next = rb_next(next);
>>>         }
>>>         return 0;
>>> --
>>> 2.43.0
>>>
>>>
>
diff mbox series

Patch

diff --git a/tools/bpf/resolve_btfids/main.c b/tools/bpf/resolve_btfids/main.c
index 27a23196d58e..440d3d066ce4 100644
--- a/tools/bpf/resolve_btfids/main.c
+++ b/tools/bpf/resolve_btfids/main.c
@@ -646,18 +646,31 @@  static int cmp_id(const void *pa, const void *pb)
 	return *a - *b;
 }
 
+static int need_bswap(int elf_byte_order)
+{
+	return __BYTE_ORDER == __LITTLE_ENDIAN && elf_byte_order != ELFDATA2LSB ||
+	       __BYTE_ORDER == __BIG_ENDIAN && elf_byte_order != ELFDATA2MSB;
+}
+
 static int sets_patch(struct object *obj)
 {
 	Elf_Data *data = obj->efile.idlist;
 	int *ptr = data->d_buf;
 	struct rb_node *next;
+	GElf_Ehdr ehdr;
+
+	if (gelf_getehdr(obj->efile.elf, &ehdr) == NULL) {
+		pr_err("FAILED cannot get ELF header: %s\n",
+			elf_errmsg(-1));
+		return -1;
+	}
 
 	next = rb_first(&obj->sets);
 	while (next) {
-		unsigned long addr, idx;
+		unsigned long addr, idx, flags;
 		struct btf_id *id;
 		int *base;
-		int cnt;
+		int cnt, i;
 
 		id   = rb_entry(next, struct btf_id, rb_node);
 		addr = id->addr[0];
@@ -679,6 +692,24 @@  static int sets_patch(struct object *obj)
 
 		qsort(base, cnt, id->is_set8 ? sizeof(uint64_t) : sizeof(int), cmp_id);
 
+		/*
+		 * When ELF endianness does not match endianness of the host,
+		 * libelf will do the translation when updating the ELF. This,
+		 * however, corrupts SET8 flags which are already in the target
+		 * endianness. So, let's bswap them to the host endianness and
+		 * libelf will then correctly translate everything.
+		 */
+		if (id->is_set8 && need_bswap(ehdr.e_ident[EI_DATA])) {
+			for (i = 0; i < cnt; i++) {
+				/*
+				 * header and entries are 8-byte, flags is the
+				 * second half of an entry
+				 */
+				flags = idx + (i + 1) * 2 + 1;
+				ptr[flags] = bswap_32(ptr[flags]);
+			}
+		}
+
 		next = rb_next(next);
 	}
 	return 0;