From: Stanislav Fomichev <sdf@google.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [linux-next:master 11295/12552] cgroup.c:undefined reference to `bpf_trampoline_link_cgroup_shim'
Date: Mon, 25 Jul 2022 09:37:20 -0700 [thread overview]
Message-ID: <CAKH8qBsQZL_rRjREwnPRXrHmn1YcfGMX5vrCuRUxyefRJBFh8A@mail.gmail.com> (raw)
In-Reply-To: <CAKH8qBudRHWs1XUVkK6g6ma62mDwc3DttTkEkjrmoS+NW=tOLw@mail.gmail.com>
On Mon, Jul 25, 2022 at 9:27 AM Stanislav Fomichev <sdf@google.com> wrote:
>
> On Sun, Jul 24, 2022 at 8:19 AM kernel test robot <lkp@intel.com> wrote:
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 18c107a1f120d095404d141dfad8f594bdc44020
> > commit: 3908fcddc65d04e069b03be49b33fae90e424631 [11295/12552] bpf: fix lsm_cgroup build errors on esoteric configs
> > config: x86_64-randconfig-a016-20220718 (https://download.01.org/0day-ci/archive/20220724/202207242322.9ymWznA0-lkp@intel.com/config)
> > compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
> > reproduce (this is a W=1 build):
> > # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=3908fcddc65d04e069b03be49b33fae90e424631
> > git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > git fetch --no-tags linux-next master
> > git checkout 3908fcddc65d04e069b03be49b33fae90e424631
> > # save the config file
> > mkdir build_dir && cp config build_dir/.config
> > make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
> >
> > If you fix the issue, kindly add following tag where applicable
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> > Note: the linux-next/master HEAD 18c107a1f120d095404d141dfad8f594bdc44020 builds fine.
> > It may have been fixed somewhere.
> >
> > All errors (new ones prefixed by >>):
> >
> > ld: vmlinux.o: in function `cgroup_bpf_release':
> > cgroup.c:(.text+0x22faf7): undefined reference to `bpf_trampoline_unlink_cgroup_shim'
> > ld: cgroup.c:(.text+0x22fb46): undefined reference to `bpf_trampoline_unlink_cgroup_shim'
> > ld: vmlinux.o: in function `__cgroup_bpf_attach':
> > >> cgroup.c:(.text+0x23039c): undefined reference to `bpf_trampoline_link_cgroup_shim'
> > ld: cgroup.c:(.text+0x2303dd): undefined reference to `bpf_trampoline_unlink_cgroup_shim'
> > ld: cgroup.c:(.text+0x230411): undefined reference to `bpf_trampoline_unlink_cgroup_shim'
> > ld: vmlinux.o: in function `__cgroup_bpf_detach':
> > cgroup.c:(.text+0x23096c): undefined reference to `bpf_trampoline_unlink_cgroup_shim'
> > ld: vmlinux.o: in function `bpf_cgroup_link_release':
> > cgroup.c:(.text+0x230a57): undefined reference to `bpf_trampoline_unlink_cgroup_shim'
>
> Hm, looks like [1] is not enough? I'll take another look..
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=9cb61fda8c71baaff423fe5be2e609100860fa78
With the config above:
$ git checkout 3908fcddc65d04e069b03be49b33fae90e424631
$ make
ld: vmlinux.o: in function `cgroup_bpf_release':
cgroup.c:(.text+0x22e8bf): undefined reference to
`bpf_trampoline_unlink_cgroup_shim'
ld: cgroup.c:(.text+0x22e90e): undefined reference to
`bpf_trampoline_unlink_cgroup_shim'
ld: vmlinux.o: in function `__cgroup_bpf_attach':
cgroup.c:(.text+0x22f164): undefined reference to
`bpf_trampoline_link_cgroup_shim'
ld: cgroup.c:(.text+0x22f1a5): undefined reference to
`bpf_trampoline_unlink_cgroup_shim'
ld: cgroup.c:(.text+0x22f1d9): undefined reference to
`bpf_trampoline_unlink_cgroup_shim'
ld: vmlinux.o: in function `__cgroup_bpf_detach':
cgroup.c:(.text+0x22f734): undefined reference to
`bpf_trampoline_unlink_cgroup_shim'
ld: vmlinux.o: in function `bpf_cgroup_link_release':
cgroup.c:(.text+0x22f81f): undefined reference to
`bpf_trampoline_unlink_cgroup_shim'
make: *** [Makefile:1164: vmlinux] Error 1
$ git checkout bpf-next
$ make olddefconfig
$ make
$
So seems fine? I'm assuming this failure is from the old next-20220722
and the latest linux-next is ok.
> > --
> > 0-DAY CI Kernel Test Service
> > https://01.org/lkp
prev parent reply other threads:[~2022-07-25 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 15:18 kernel test robot
2022-07-25 16:27 ` Stanislav Fomichev
2022-07-25 16:37 ` Stanislav Fomichev [this message]
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=CAKH8qBsQZL_rRjREwnPRXrHmn1YcfGMX5vrCuRUxyefRJBFh8A@mail.gmail.com \
--to=sdf@google.com \
--cc=ast@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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