From: kbuild test robot <lkp@intel.com>
To: Yonghong Song <yhs@fb.com>
Cc: kbuild-all@01.org, peterz@infradead.org, ast@fb.com,
daniel@iogearbox.net, netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH net-next v2 1/2] bpf: add support for sys_enter_* and sys_exit_* tracepoints
Date: Thu, 3 Aug 2017 21:47:43 +0800 [thread overview]
Message-ID: <201708032130.rnCsVne6%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170803052828.2303723-2-yhs@fb.com>
[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]
Hi Yonghong,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Yonghong-Song/bpf-add-support-for-sys_-enter-exit-_-tracepoints/20170803-213504
config: i386-randconfig-x019-201731 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/events/core.c: In function 'perf_event_set_bpf_prog':
>> kernel/events/core.c:8073:18: error: implicit declaration of function 'is_syscall_trace_event' [-Werror=implicit-function-declaration]
is_syscall_tp = is_syscall_trace_event(event->tp_event);
^~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/is_syscall_trace_event +8073 kernel/events/core.c
8059
8060 static int perf_event_set_bpf_prog(struct perf_event *event, u32 prog_fd)
8061 {
8062 bool is_kprobe, is_tracepoint, is_syscall_tp;
8063 struct bpf_prog *prog;
8064
8065 if (event->attr.type != PERF_TYPE_TRACEPOINT)
8066 return perf_event_set_bpf_handler(event, prog_fd);
8067
8068 if (event->tp_event->prog)
8069 return -EEXIST;
8070
8071 is_kprobe = event->tp_event->flags & TRACE_EVENT_FL_UKPROBE;
8072 is_tracepoint = event->tp_event->flags & TRACE_EVENT_FL_TRACEPOINT;
> 8073 is_syscall_tp = is_syscall_trace_event(event->tp_event);
8074 if (!is_kprobe && !is_tracepoint && !is_syscall_tp)
8075 /* bpf programs can only be attached to u/kprobe or tracepoint */
8076 return -EINVAL;
8077
8078 prog = bpf_prog_get(prog_fd);
8079 if (IS_ERR(prog))
8080 return PTR_ERR(prog);
8081
8082 if ((is_kprobe && prog->type != BPF_PROG_TYPE_KPROBE) ||
8083 (is_tracepoint && prog->type != BPF_PROG_TYPE_TRACEPOINT) ||
8084 (is_syscall_tp && prog->type != BPF_PROG_TYPE_TRACEPOINT)) {
8085 /* valid fd, but invalid bpf program type */
8086 bpf_prog_put(prog);
8087 return -EINVAL;
8088 }
8089
8090 if (is_tracepoint) {
8091 int off = trace_event_get_offsets(event->tp_event);
8092
8093 if (prog->aux->max_ctx_offset > off) {
8094 bpf_prog_put(prog);
8095 return -EACCES;
8096 }
8097 }
8098 event->tp_event->prog = prog;
8099
8100 return 0;
8101 }
8102
---
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: 27387 bytes --]
next prev parent reply other threads:[~2017-08-03 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 5:28 [PATCH net-next v2 0/2] bpf: add support for sys_{enter|exit}_* tracepoints Yonghong Song
2017-08-03 5:28 ` [PATCH net-next v2 1/2] bpf: add support for sys_enter_* and sys_exit_* tracepoints Yonghong Song
2017-08-03 8:08 ` Peter Zijlstra
2017-08-03 15:22 ` Yonghong Song
2017-08-03 13:47 ` kbuild test robot [this message]
2017-08-03 5:28 ` [PATCH net-next v2 2/2] bpf: add a test case for syscalls/sys_{enter|exit}_* tracepoints Yonghong Song
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=201708032130.rnCsVne6%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).