From: kernel test robot <lkp@intel.com>
To: Delyan Kratunov <delyank@fb.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: [linux-next:master 3054/6195] trace_uprobe.c:undefined reference to `bpf_stats_enabled_key'
Date: Wed, 29 Jun 2022 06:28:17 +0800 [thread overview]
Message-ID: <202206290627.FEONIjoZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cb71b93c2dc36d18a8b05245973328d018272cdf
commit: 8c7dcb84e3b744b2b70baa7a44a9b1881c33a9c9 [3054/6195] bpf: implement sleepable uprobes by chaining gps
config: mips-randconfig-r016-20220628 (https://download.01.org/0day-ci/archive/20220629/202206290627.FEONIjoZ-lkp@intel.com/config)
compiler: mipsel-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8c7dcb84e3b744b2b70baa7a44a9b1881c33a9c9
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 8c7dcb84e3b744b2b70baa7a44a9b1881c33a9c9
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=mips 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 cb71b93c2dc36d18a8b05245973328d018272cdf builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
mipsel-linux-ld: kernel/trace/trace_uprobe.o: in function `__uprobe_perf_func':
>> trace_uprobe.c:(.text+0x5388): undefined reference to `bpf_stats_enabled_key'
>> mipsel-linux-ld: trace_uprobe.c:(.text+0x5434): undefined reference to `bpf_stats_enabled_key'
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-28 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202206290627.FEONIjoZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=delyank@fb.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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