Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp10143308pxu; Tue, 29 Dec 2020 15:30:16 -0800 (PST) X-Google-Smtp-Source: ABdhPJz15dAXqvrT2fB7UHVx551eU/Fd/S+T1jnVddSpvmcuDLb678qbhIRrTERiECMrrhar5Vfm X-Received: by 2002:a05:6402:404:: with SMTP id q4mr49354857edv.295.1609284615982; Tue, 29 Dec 2020 15:30:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609284615; cv=none; d=google.com; s=arc-20160816; b=GqItrUPruE3KTSfIPm/9vdoQrD96wj6cQduU6/k7VtNKsbEqmxinelkEqj2pPgt0c/ sqZarRL2L6uti88MF+YXZl9rHkoHl7HjUrohBkY9ZqTybcF0ZUVmbpjgbfsL8anHCSru sqP5LVq3UyzoDlrufmpmcBfdZDpq7wT1B38QIH+/FTZ6T2GLEkpEapeFsKL1ihnOJ8nL QEPwvtvi8/UktzfM0lZh95bHF/ejG+S3vV9NgWFPSNeyw57nwUKc9yvPfroXOZw378KF FtprygN6Osp0UNgss37/9I46TtJDt9a7dyRLtYuubADVgA/eF4Kswz2VOYHFpqUyL0+D 0ccQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=L6/vysuHe7ecBF8UT88/4+9bpG31A0RQHHTtLzTOrus=; b=ffbtSoBd4iIGOCFXDp5a8WJgceb9esvMsHQKJsmVHhpCAnBw0zbdL5nV8MlTcX1L29 O9KK8A72lyAjBNElDZo6fqANUGxdngPA71Shj8AKai8tZo0siEhKZKlCfUB/Lv7krcp9 la0+ZJSRTy8x2M+yGBa0WzISGmxIvD9valG3N7YNhd2HAmVLZgZ0cRHIJQZRv616lVuf SEI+IVHnhoccnIEKgMMp7J2JCC4myCEZrRyv3UmColkwIKO3EKKROWZQWys5cKFkrbir ZvOOb7mDHY2CDdPMb6Zuhy5KNt68D7wzO7wcsM16D3+AEXymQ3wRAAYfXAVHqP3Yi95b Hb+A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v4si22154585edt.439.2020.12.29.15.29.52; Tue, 29 Dec 2020 15:30:15 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726274AbgL2X3Z (ORCPT + 99 others); Tue, 29 Dec 2020 18:29:25 -0500 Received: from foss.arm.com ([217.140.110.172]:50358 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726161AbgL2X3Y (ORCPT ); Tue, 29 Dec 2020 18:29:24 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id C8C9030E; Tue, 29 Dec 2020 15:28:38 -0800 (PST) Received: from e107158-lin (e107158-lin.cambridge.arm.com [10.1.194.78]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A99CB3F6CF; Tue, 29 Dec 2020 15:28:37 -0800 (PST) Date: Tue, 29 Dec 2020 23:28:35 +0000 From: Qais Yousef To: Jiri Olsa Cc: Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Jiri Olsa , netdev@vger.kernel.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: BTFIDS: FAILED unresolved symbol udp6_sock Message-ID: <20201229232835.cbyfmja3bu3lx7we@e107158-lin> References: <20201229151352.6hzmjvu3qh6p2qgg@e107158-lin> <20201229173401.GH450923@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20201229173401.GH450923@krava> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jiri On 12/29/20 18:34, Jiri Olsa wrote: > On Tue, Dec 29, 2020 at 03:13:52PM +0000, Qais Yousef wrote: > > Hi > > > > When I enable CONFIG_DEBUG_INFO_BTF I get the following error in the BTFIDS > > stage > > > > FAILED unresolved symbol udp6_sock > > > > I cross compile for arm64. My .config is attached. > > > > I managed to reproduce the problem on v5.9 and v5.10. Plus 5.11-rc1. > > > > Have you seen this before? I couldn't find a specific report about this > > problem. > > > > Let me know if you need more info. > > hi, > this looks like symptom of the gcc DWARF bug we were > dealing with recently: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97060 > https://lore.kernel.org/lkml/CAE1WUT75gu9G62Q9uAALGN6vLX=o7vZ9uhqtVWnbUV81DgmFPw@mail.gmail.com/#r > > what pahole/gcc version are you using? I'm on gcc 9.3.0 aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0 I was on pahole v1.17. I moved to v1.19 but I still see the same problem. Thanks -- Qais Yousef > > we fixed pahole (v1.19) to workaround the issue and AFAIK > there's already gcc fix as well