From: Veronika Kabatova <vkabatov@redhat.com>
To: bpf <bpf@vger.kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>
Subject: Build failures: unresolved symbol vfs_getattr
Date: Mon, 14 Sep 2020 10:48:36 -0400 (EDT) [thread overview]
Message-ID: <748495289.11017858.1600094916732.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1723352278.11013122.1600093319730.JavaMail.zimbra@redhat.com>
Hello,
we tested the bpf-next tree with CKI and ran across build failures. The
important part of the build log is:
00:18:05 GEN .version
00:18:05 CHK include/generated/compile.h
00:18:05 LD vmlinux.o
00:18:27 MODPOST vmlinux.symvers
00:18:27 MODINFO modules.builtin.modinfo
00:18:27 GEN modules.builtin
00:18:27 LD .tmp_vmlinux.btf
00:18:42 BTF .btf.vmlinux.bin.o
00:19:13 LD .tmp_vmlinux.kallsyms1
00:19:19 KSYM .tmp_vmlinux.kallsyms1.o
00:19:22 LD .tmp_vmlinux.kallsyms2
00:19:25 KSYM .tmp_vmlinux.kallsyms2.o
00:19:28 LD vmlinux
00:19:40 BTFIDS vmlinux
00:19:40 FAILED unresolved symbol vfs_getattr
00:19:40 make[2]: *** [Makefile:1167: vmlinux] Error 255
00:19:40 make[1]: *** [scripts/Makefile.package:109: targz-pkg] Error 2
00:19:40 make: *** [Makefile:1528: targz-pkg] Error 2
Going git-bisect style, the issue is introduced by the patch series in [0].
Commit 2532f849b5134c4c62a20e5aaca33d9fb08af528 (last one before the
mentioned series were merged) passes, testing of
cd04b04de119a222c83936f7e9dbd46a650cb688 (last patch of the series)
fails. The failure is still present with the current top of the tree.
The kernel config used is a Fedora 32 config base + olddefconfig +
kselftest-merge, you can grab it directly from [1]. Environment is
Fedora rawhide.
The failure is easily reproduced with our container image that already
has all the needed dependencies installed:
registry.gitlab.com/cki-project/containers/builder-rawhide:latest
Steps to reproduce after starting the image:
git clone https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git --depth 1
curl https://gitlab.com/-/snippets/2014934/raw -o bpf-next/.config
cd bpf-next/
make -j 10 INSTALL_MOD_STRIP=1 targz-pkg
I already notified Jirka (cced) earlier today but am also sending a
bug report here in case someone else runs into the issue.
I can help with testing of potential fixes if it's needed.
Veronika
[0]: https://lore.kernel.org/bpf/20200825192124.710397-1-jolsa@kernel.org/
[1]: https://gitlab.com/-/snippets/2014934/raw
next parent reply other threads:[~2020-09-14 14:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1723352278.11013122.1600093319730.JavaMail.zimbra@redhat.com>
2020-09-14 14:48 ` Veronika Kabatova [this message]
2020-09-14 18:25 ` Build failures: unresolved symbol vfs_getattr Jiri Olsa
2020-09-14 22:26 ` Andrii Nakryiko
2020-09-15 7:30 ` Jiri Olsa
2020-09-15 12:17 ` Jiri Olsa
2020-09-16 9:06 ` Jiri Olsa
2020-10-16 21:38 ` Jiri Olsa
2020-10-21 19:42 ` Jiri Olsa
2020-10-22 20:00 ` Andrii Nakryiko
2020-10-23 5:36 ` Jiri Olsa
2020-10-23 6:58 ` Jiri Olsa
2020-10-23 18:22 ` Andrii Nakryiko
2020-10-23 20:17 ` Jiri Olsa
2020-10-23 20:32 ` Andrii Nakryiko
2020-10-23 20:45 ` Jiri Olsa
2020-10-23 22:02 ` Andrii Nakryiko
2020-10-26 10:14 ` Jiri Olsa
2020-10-26 22:06 ` Andrii Nakryiko
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=748495289.11017858.1600094916732.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=jolsa@redhat.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