From: Daniel Borkmann <daniel@iogearbox•net>
To: kbuild test robot <lkp@intel•com>
Cc: kbuild-all@01•org, davem@davemloft•net,
alexei.starovoitov@gmail•com, tgraf@suug•ch,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
Alexei Starovoitov <ast@kernel•org>
Subject: Re: [PATCH net-next 2/2] bpf: add event output helper for notifications/sampling/logging
Date: Mon, 18 Apr 2016 09:22:15 +0200 [thread overview]
Message-ID: <57148B27.60001@iogearbox.net> (raw)
In-Reply-To: <201604180722.wizpe3nL%fengguang.wu@intel.com>
On 04/18/2016 01:55 AM, kbuild test robot wrote:
> Hi Daniel,
>
> [auto build test ERROR on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Daniel-Borkmann/bpf-trace-add-BPF_F_CURRENT_CPU-flag-for-bpf_perf_event_output/20160418-063147
> config: m68k-allyesconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=m68k
>
> All errors (new ones prefixed by >>):
>
> net/core/filter.c: In function 'bpf_skb_event_output':
>>> net/core/filter.c:1599:2: error: implicit declaration of function 'perf_fetch_caller_regs' [-Werror=implicit-function-declaration]
> perf_fetch_caller_regs(regs);
> ^
> cc1: some warnings being treated as errors
>
> vim +/perf_fetch_caller_regs +1599 net/core/filter.c
>
> 1593 static DEFINE_PER_CPU(struct pt_regs, bpf_pt_regs);
> 1594
> 1595 static u64 bpf_skb_event_output(u64 r1, u64 r2, u64 flags, u64 r4, u64 size)
> 1596 {
> 1597 struct pt_regs *regs = this_cpu_ptr(&bpf_pt_regs);
> 1598
>> 1599 perf_fetch_caller_regs(regs);
> 1600
> 1601 return bpf_perf_event_output((long)regs, r2, flags, r4, size);
> 1602 }
Sorry about that, missed this one. Will fix it up in v2!
Thanks,
Daniel
prev parent reply other threads:[~2016-04-18 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 22:29 [PATCH net-next 0/2] BPF updates Daniel Borkmann
2016-04-17 22:29 ` [PATCH net-next 1/2] bpf, trace: add BPF_F_CURRENT_CPU flag for bpf_perf_event_output Daniel Borkmann
2016-04-17 22:29 ` [PATCH net-next 2/2] bpf: add event output helper for notifications/sampling/logging Daniel Borkmann
2016-04-17 23:55 ` kbuild test robot
2016-04-18 7:22 ` Daniel Borkmann [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=57148B27.60001@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=alexei.starovoitov@gmail$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=kbuild-all@01$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lkp@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tgraf@suug$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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