From: kbuild test robot <fengguang.wu@intel.com>
To: Josef Bacik <jbacik@fb.com>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org
Subject: [josef-btrfs:bpf-override-return 1/2] bpf_trace.c:undefined reference to `trace_kprobe_ftrace'
Date: Thu, 2 Nov 2017 04:17:56 +0800 [thread overview]
Message-ID: <201711020454.cW6EivbY%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git bpf-override-return
head: 4c8ff03808e83b25a9771d1171741d550072ba36
commit: 4608d4f4e271703f1609a78c9c0ac2f5d1fb59a2 [1/2] bpf: add a bpf_override_function helper
config: i386-randconfig-x0-11020159 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 4608d4f4e271703f1609a78c9c0ac2f5d1fb59a2
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/trace/bpf_trace.o: In function `perf_event_attach_bpf_prog':
>> bpf_trace.c:(.text+0xe43): undefined reference to `trace_kprobe_ftrace'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 23766 bytes --]
reply other threads:[~2017-11-01 20:18 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=201711020454.cW6EivbY%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=jbacik@fb.com \
--cc=kbuild-all@01.org \
--cc=linux-btrfs@vger.kernel.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).