From: Ming Lei <tom.leiming@gmail.com>
To: Amy Parker <enbyamy@gmail.com>
Cc: linux-kbuild@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
masahiroy@kernel.org, michal.lkml@markovi.net,
Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>
Subject: Re: 5.10 tree fails to build
Date: Mon, 9 Nov 2020 17:57:37 +0800 [thread overview]
Message-ID: <CACVXFVNmYoh20atwG9DOE-ZXFMLqNgGucREBsWAEYnDV4eLs1Q@mail.gmail.com> (raw)
In-Reply-To: <CAE1WUT75gu9G62Q9uAALGN6vLX=o7vZ9uhqtVWnbUV81DgmFPw@mail.gmail.com>
On Thu, Nov 5, 2020 at 12:58 PM Amy Parker <enbyamy@gmail.com> wrote:
>
> On all attempts to build the 5.10 tree (from either release candidate,
> Linus's tree, Greg's tree, etc), the build crashes on the BTFID vmlinux
> stage. I've tested this on several different devices with completely
> different hardware and kernel configs. The symbol for vfs_getattr
> appears to be missing. Compiles for all of these work on any compile
> on any 5.9 tree. I've tested all 4 5.9 dot-releases as well as the first
> two and last two release candidates and Greg's staging tree.
>
> The specific error is:
> BTFIDS vmlinux
> FAILED unresolved symbol vfs_getattr
> make: *** [Makefile:1164: vmlinux] Error 255
>
> Any thoughts as to what's causing this? The main machine I'm
> compiling with is running kernel 5.8.17 with dwarves 1.17. My
> kernel config is attached as `kernel_config`.
Turns out the issue is introduced in the following commit:
commit 6e22ab9da79343532cd3cde39df25e5a5478c692
Author: Jiri Olsa <jolsa@kernel.org>
Date: Tue Aug 25 21:21:20 2020 +0200
bpf: Add d_path helper
The issue can be observed reliably when building kernel in Fedora 33 with
F33's kernel config.
GCC: gcc version 10.2.1 20200826 (Red Hat 10.2.1-3) (GCC)
--
Ming Lei
next prev parent reply other threads:[~2020-11-09 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 3:12 5.10 tree fails to build Amy Parker
2020-11-09 9:57 ` Ming Lei [this message]
2020-11-09 10:32 ` Jiri Olsa
2020-11-09 17:31 ` Arnaldo Carvalho de Melo
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=CACVXFVNmYoh20atwG9DOE-ZXFMLqNgGucREBsWAEYnDV4eLs1Q@mail.gmail.com \
--to=tom.leiming@gmail.com \
--cc=ast@kernel.org \
--cc=enbyamy@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=torvalds@linux-foundation.org \
/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).