linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@fb.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Kees Cook <keescook@chromium.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <bpf@vger.kernel.org>
Subject: Re: CLANG LTO compatibility issue with DEBUG_INFO_BTF
Date: Thu, 18 Mar 2021 20:56:46 -0700	[thread overview]
Message-ID: <4e1d1504-55e5-db8b-112b-921d86ef7d5b@fb.com> (raw)
In-Reply-To: <20210319113730.7ad6a609@xhacker.debian>



On 3/18/21 8:45 PM, Jisheng Zhang wrote:
> Hi,
> 
> When trying the latest 5.12-rc3 with both LTO_CLANG_THIN and DEBUG_INFO_BTF
> enabled, I met lots of warnings such as:
> 
> ...
> tag__recode_dwarf_type: couldn't find 0x4a7ade5 type for 0x4ab9f88 (subroutine_type)!
> ftype__recode_dwarf_types: couldn't find 0x4a7ade5 type for 0x4ab9fa4 (formal_parameter)!
> ...
> namespace__recode_dwarf_types: couldn't find 0x4a8ff4a type for 0x4aba05c (member)!
> namespace__recode_dwarf_types: couldn't find 0x4a7ae9b type for 0x4aba084 (member)!
> ...
> WARN: multiple IDs found for 'path': 281, 729994 - using 281
> WARN: multiple IDs found for 'task_struct': 421, 730101 - using 421
> ...
> 
> 
> then finally get build error:
> FAILED unresolved symbol vfs_truncate
> 
> 
> Is this a known issue? Do we need to make DEBUG_INFO_BTF depend on !LTO?

This is a known issue for pahole. pahole does not handle dwarf well 
generated with LTO. Bill Wendling from google is looking at the issue 
and I will help look at the issue as well. Since bpf heavily depends
on BTF, at this point, I suggest if you are using bpf, please do not
turn on LTO. Or if you build with LTO, just turn off DEBUG_INFO_BTF
in your config. Thanks!

> 
> pahole version: v1.20
> clang version: 11.0
> 
> 
> Thanks
> 

  reply	other threads:[~2021-03-19  3:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  3:45 CLANG LTO compatibility issue with DEBUG_INFO_BTF Jisheng Zhang
2021-03-19  3:56 ` Yonghong Song [this message]
2021-03-22  1:48   ` Jisheng Zhang

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=4e1d1504-55e5-db8b-112b-921d86ef7d5b@fb.com \
    --to=yhs@fb.com \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samitolvanen@google.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).