BPF List
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@fb.com>
To: Lorenz Bauer <lmb@cloudflare.com>, Andrii Nakryiko <andrii@kernel.org>
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: bpf_core_type_id_kernel with qualifier aborts clang compilation
Date: Thu, 4 Mar 2021 08:41:52 -0800	[thread overview]
Message-ID: <a3782f71-3f6b-1e75-17a9-1827822c2030@fb.com> (raw)
In-Reply-To: <CACAyw9_P-Zk+hrOwgenLz4hCc7Cae9=qV86Td2CkGVUPAzWQ8A@mail.gmail.com>



On 3/4/21 3:25 AM, Lorenz Bauer wrote:
> Hi Yonghong, Andrii,
> 
> Some more poking at CO-RE. The code below leads to a compiler error:
> 
> struct s {
>      int _1;
>      char _2;
> };
> 
> __section("socket_filter/type_ids") int type_ids() {
>      return bpf_core_type_id_kernel(const struct s);
> }
> 
> Truncated output:
> fatal error: error in backend: Empty type name for BTF_TYPE_ID_REMOTE reloc
> PLEASE submit a bug report to https://bugs.llvm.org/  and include the
> crash backtrace, preprocessed source, and associated run script.
> Stack dump:
> 0.    Program arguments: clang-12 -target bpf -O2 -g -Wall -Werror
> -mlittle-endian -c internal/btf/testdata/relocs.c -o
> internal/btf/testdata/relocs-el.elf
> 1.    <eof> parser at end of file
> 2.    Per-function optimization
> 3.    Running pass 'BPF Preserve Debuginfo Type' on function '@type_ids'
> ...
> clang: error: clang frontend command failed with exit code 70 (use -v
> to see invocation)
> Ubuntu clang version
> 12.0.0-++20210126113614+510b3d4b3e02-1~exp1~20210126104320.178
> Target: bpf
> 
> "volatile" has the same problem. Interestingly, the same code works
> for bpf_core_type_id_local. Is this expected?

First, bpf_core_type_id_local() works as compiler did not check type 
name. for bpf_core_type_id_local(), there is no relocation, libbpf
may need to adjust type id if it tries to do btf dedup, merging, etc.

Second, the above bpf_core_type_id_kernel() failed due to
"const" (or "volatile") modifier. bpf_core_type_id_kernel()
requires a type name as relocation will be performed.
In the current implementation, the btf type is
    const -> struct s
and there is no name for "const", that is why compiler issues
an explicit fatal error:
     fatal error: error in backend: Empty type name for 
BTF_TYPE_ID_REMOTE reloc

To fix the issue, just do not use any modifier,
   bpf_core_type_id_kernel(struct s)
should work fine.

I think in the case, it would be good if the compiler tries
to peel off modifiers and find the ultimate type name
instead of fatal error. I will put a patch on this.

Thanks for reporting!

> 
> Best
> Lorenz
> 

  reply	other threads:[~2021-03-04 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 11:25 bpf_core_type_id_kernel with qualifier aborts clang compilation Lorenz Bauer
2021-03-04 16:41 ` Yonghong Song [this message]
2021-03-05 21:36   ` Yonghong Song
2021-03-08  9:33     ` Lorenz Bauer

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=a3782f71-3f6b-1e75-17a9-1827822c2030@fb.com \
    --to=yhs@fb.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=lmb@cloudflare.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