From: kbuild test robot <lkp@intel.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: kbuild-all@01.org, luto@amacapital.net, davem@davemloft.net,
daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org, kernel-team@fb.com,
linux-api@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf, capabilities: introduce CAP_BPF
Date: Wed, 28 Aug 2019 18:38:16 +0800 [thread overview]
Message-ID: <201908281810.Rg8jReyH%lkp@intel.com> (raw)
In-Reply-To: <20190827205213.456318-1-ast@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
Hi Alexei,
I love your patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Alexei-Starovoitov/bpf-capabilities-introduce-CAP_BPF/20190828-142441
base: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: ia64-defconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=ia64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/bpf/core.c: In function 'cap_bpf_tracing':
>> kernel/bpf/core.c:2110:31: error: implicit declaration of function 'perf_paranoid_tracepoint_raw' [-Werror=implicit-function-declaration]
(capable(CAP_BPF) && !perf_paranoid_tracepoint_raw());
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/perf_paranoid_tracepoint_raw +2110 kernel/bpf/core.c
2106
2107 bool cap_bpf_tracing(void)
2108 {
2109 return capable(CAP_SYS_ADMIN) ||
> 2110 (capable(CAP_BPF) && !perf_paranoid_tracepoint_raw());
2111 }
2112
---
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: 19214 bytes --]
prev parent reply other threads:[~2019-08-28 10:39 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 20:52 [PATCH bpf-next] bpf, capabilities: introduce CAP_BPF Alexei Starovoitov
2019-08-27 23:01 ` Andy Lutomirski
2019-08-27 23:21 ` Steven Rostedt
2019-08-27 23:34 ` Andy Lutomirski
2019-08-28 0:44 ` Steven Rostedt
2019-08-28 1:12 ` Andy Lutomirski
2019-08-28 2:22 ` Steven Rostedt
2019-08-28 0:38 ` Alexei Starovoitov
2019-08-28 3:30 ` Masami Hiramatsu
2019-08-28 4:47 ` Alexei Starovoitov
2019-08-28 0:34 ` Alexei Starovoitov
2019-08-28 0:55 ` Andy Lutomirski
2019-08-28 2:00 ` Andy Lutomirski
2019-08-28 4:49 ` Alexei Starovoitov
2019-08-28 6:20 ` Andy Lutomirski
2019-08-28 23:38 ` Alexei Starovoitov
2019-08-29 0:58 ` Andy Lutomirski
2019-08-28 4:43 ` Alexei Starovoitov
2019-08-28 6:12 ` Andy Lutomirski
2019-08-28 22:55 ` Alexei Starovoitov
2019-08-29 0:45 ` Andy Lutomirski
2019-08-29 0:53 ` Andy Lutomirski
2019-08-29 4:07 ` Alexei Starovoitov
2019-09-28 23:37 ` Steven Rostedt
2019-09-30 18:31 ` Kees Cook
2019-10-01 1:22 ` Alexei Starovoitov
2019-10-01 22:10 ` Steven Rostedt
2019-10-01 22:18 ` Alexei Starovoitov
2019-10-01 22:47 ` Steven Rostedt
2019-10-02 17:18 ` Alexei Starovoitov
2019-10-02 23:00 ` Steven Rostedt
2019-10-03 16:18 ` trace_printk issue. Was: " Alexei Starovoitov
2019-10-03 16:41 ` Steven Rostedt
2019-10-04 19:56 ` Alexei Starovoitov
2019-10-03 6:12 ` Masami Hiramatsu
2019-10-03 16:20 ` Alexei Starovoitov
2019-08-28 7:14 ` Peter Zijlstra
2019-08-28 22:08 ` Alexei Starovoitov
2019-08-29 13:34 ` Steven Rostedt
2019-08-29 15:43 ` Andy Lutomirski
2019-08-29 17:23 ` Alexei Starovoitov
2019-08-29 17:36 ` Andy Lutomirski
2019-08-29 17:49 ` Steven Rostedt
2019-08-29 17:19 ` Alexei Starovoitov
2019-08-29 17:47 ` Steven Rostedt
2019-08-28 10:38 ` kbuild test robot [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=201908281810.Rg8jReyH%lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=linux-api@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@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).