From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-12.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9C650C433DB for ; Mon, 11 Jan 2021 22:35:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6410D22D00 for ; Mon, 11 Jan 2021 22:35:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389431AbhAKWfi (ORCPT ); Mon, 11 Jan 2021 17:35:38 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:20983 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387685AbhAKWfi (ORCPT ); Mon, 11 Jan 2021 17:35:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610404451; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=u8wvNzKHbCZNUsD83LMMeksH/oMSQX1O0M/D4dVfyQY=; b=dhDcYdTk9SKgDxVPLjWn3lucWu22cke9s7zRkQwUDPjsPPsJRrWZ/t26p/C2nA+Q0TcTdh DW8eGfPN57uWVff3wR8YVNgQjSH3uKCMtcnXdAUXCVbr5mwvctQ/GUgch8TZPbGf29hSg5 Sxnt4lSFGpnsBfGkM6EHRhyjdyVrhVo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-452-hkyCXt0CPaam7ZZh2m3OAQ-1; Mon, 11 Jan 2021 17:34:07 -0500 X-MC-Unique: hkyCXt0CPaam7ZZh2m3OAQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id DF376803620; Mon, 11 Jan 2021 22:34:05 +0000 (UTC) Received: from tstellar.remote.csb (ovpn-114-95.phx2.redhat.com [10.3.114.95]) by smtp.corp.redhat.com (Postfix) with ESMTP id C0C7150DE3; Mon, 11 Jan 2021 22:34:04 +0000 (UTC) Reply-To: tstellar@redhat.com Subject: Re: Check pahole availibity and BPF support of toolchain before starting a Linux kernel build To: Jiri Olsa , Sedat Dilek Cc: Andrii Nakryiko , Jiri Olsa , Yonghong Song , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , John Fastabend , KP Singh , Masahiro Yamada , bpf , Linux Kbuild mailing list References: <20210111223144.GA1250730@krava> From: Tom Stellard Organization: Red Hat Message-ID: Date: Mon, 11 Jan 2021 14:34:04 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20210111223144.GA1250730@krava> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org 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 >