From: kbuild test robot <lkp@intel.com>
To: Yonghong Song <yhs@fb.com>
Cc: kbuild-all@01.org, ast@fb.com, daniel@iogearbox.net,
netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 2/9] bpf: add bpf_get_stack helper
Date: Wed, 18 Apr 2018 21:49:27 +0800 [thread overview]
Message-ID: <201804182142.fK1WIiI7%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180417174642.3342753-3-yhs@fb.com>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
Hi Yonghong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Yonghong-Song/bpf-add-bpf_get_stack-helper/20180418-210810
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 7.2.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
make.cross ARCH=ia64
All errors (new ones prefixed by >>):
kernel/bpf/core.c: In function 'bpf_prog_free_deferred':
>> kernel/bpf/core.c:1714:3: error: implicit declaration of function 'put_callchain_buffers' [-Werror=implicit-function-declaration]
put_callchain_buffers();
^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/put_callchain_buffers +1714 kernel/bpf/core.c
1704
1705 static void bpf_prog_free_deferred(struct work_struct *work)
1706 {
1707 struct bpf_prog_aux *aux;
1708 int i;
1709
1710 aux = container_of(work, struct bpf_prog_aux, work);
1711 if (bpf_prog_is_dev_bound(aux))
1712 bpf_prog_offload_destroy(aux->prog);
1713 if (aux->prog->need_callchain_buf)
> 1714 put_callchain_buffers();
1715 for (i = 0; i < aux->func_cnt; i++)
1716 bpf_jit_free(aux->func[i]);
1717 if (aux->func_cnt) {
1718 kfree(aux->func);
1719 bpf_prog_unlock_free(aux->prog);
1720 } else {
1721 bpf_jit_free(aux->prog);
1722 }
1723 }
1724
---
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: 49847 bytes --]
next prev parent reply other threads:[~2018-04-18 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 17:46 [PATCH bpf-next 0/9] bpf: add bpf_get_stack helper Yonghong Song
2018-04-17 17:46 ` [PATCH bpf-next 1/9] bpf: change prototype for stack_map_get_build_id_offset Yonghong Song
2018-04-17 17:46 ` [PATCH bpf-next 2/9] bpf: add bpf_get_stack helper Yonghong Song
2018-04-18 13:49 ` kbuild test robot [this message]
2018-04-17 17:46 ` [PATCH bpf-next 3/9] bpf/verifier: refine retval R0 state for " Yonghong Song
2018-04-17 17:46 ` [PATCH bpf-next 4/9] bpf/verifier: improve register value range tracking with ARSH Yonghong Song
2018-04-17 17:46 ` [PATCH bpf-next 5/9] tools/bpf: add bpf_get_stack helper to tools headers Yonghong Song
2018-04-17 17:46 ` [PATCH bpf-next 6/9] samples/bpf: move common-purpose perf_event functions to bpf_load.c Yonghong Song
2018-04-17 17:46 ` [PATCH bpf-next 7/9] samples/bpf: add a test for bpf_get_stack helper Yonghong Song
2018-04-17 17:46 ` [PATCH bpf-next 8/9] tools/bpf: add a verifier test case for bpf_get_stack helper and ARSH Yonghong Song
2018-04-17 17:46 ` [PATCH bpf-next 9/9] tools/bpf: add a test_progs test case for bpf_get_stack helper 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=201804182142.fK1WIiI7%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=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