bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Stellard <tstellar@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>, Sedat Dilek <sedat.dilek@gmail.com>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Jiri Olsa <jolsa@kernel.org>, Yonghong Song <yhs@fb.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>, bpf <bpf@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: Check pahole availibity and BPF support of toolchain before starting a Linux kernel build
Date: Mon, 11 Jan 2021 14:34:04 -0800	[thread overview]
Message-ID: <ed779f29-18b9-218f-a937-878328a769fe@redhat.com> (raw)
In-Reply-To: <20210111223144.GA1250730@krava>

On 1/11/21 2:31 PM, Jiri Olsa wrote:
> On Mon, Jan 11, 2021 at 10:30:22PM +0100, Sedat Dilek wrote:
> 
> SNIP
> 
>>>>
>>>> Building a new Linux-kernel...
>>>>
>>>> - Sedat -
>>>>
>>>> [1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/
>>>> [2] https://github.com/ClangBuiltLinux/tc-build/issues/129#issuecomment-758026878
>>>> [3] https://github.com/ClangBuiltLinux/tc-build/issues/129#issuecomment-758056553
>>>
>>> There are no significant bug fixes between pahole 1.19 and master that
>>> would solve this problem, so let's try to repro this.
>>>
>>
>> You are right pahole fom latest Git does not solve the issue.
>>
>> + info BTFIDS vmlinux
>> + [  != silent_ ]
>> + printf   %-7s %s\n BTFIDS vmlinux
>>   BTFIDS  vmlinux
>> + ./tools/bpf/resolve_btfids/resolve_btfids vmlinux
>> FAILED: load BTF from vmlinux: Invalid argument
> 
> hm, is there a .BTF section in vmlinux?
> 
> is this working over vmlinux:
>   $ bpftool btf dump file ./vmlinux
> 
> do you have a verbose build output? I'd think pahole scream first..
> 

It does.  For me, pahole segfaults at scripts/link-vmlinux.sh:131.  This 
is pretty easy for me to reproduce.  I have logs, what other information 
would be helpful?  How about a pahole backtrace?

-Tom

> jirka
> 


  reply	other threads:[~2021-01-11 22:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 12:48 Check pahole availibity and BPF support of toolchain before starting a Linux kernel build Sedat Dilek
2021-01-11 16:05 ` Yonghong Song
2021-01-11 17:56   ` Sedat Dilek
2021-01-11 21:03     ` Andrii Nakryiko
     [not found]       ` <CA+icZUVrF_LCVhELbNLA7=FzEZK4=jk3QLD9XT2w5bQNo=nnOA@mail.gmail.com>
2021-01-11 22:31         ` Jiri Olsa
2021-01-11 22:34           ` Tom Stellard [this message]
2021-01-12 10:46             ` Jiri Olsa
2021-01-12 13:10               ` Jiri Olsa
2021-01-12 16:14                 ` Sedat Dilek
2021-01-12 16:21                   ` Jiri Olsa
2021-01-12 17:18                     ` Sedat Dilek
2021-01-12 20:47                     ` Sedat Dilek
2021-01-12 21:36                       ` Sedat Dilek
2021-01-14 14:13           ` Sedat Dilek
2021-01-14 14:24             ` Jiri Olsa
2021-01-14 14:29               ` Sedat Dilek
     [not found]                 ` <CA+icZUXp5gkxCr+mybQ8uO3xx+rVmmRSnN7Dfx0Xmr+VQWyZAA@mail.gmail.com>
2021-01-14 15:13                   ` Sedat Dilek
2021-01-12  0:57         ` Yonghong Song
2021-01-12  4:09           ` Sedat Dilek

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=ed779f29-18b9-218f-a937-878328a769fe@redhat.com \
    --to=tstellar@redhat.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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).