From: kernel test robot <lkp@intel.com>
To: Stanislav Fomichev <sdf@google.com>, bpf@vger.kernel.org
Cc: kbuild-all@lists.01.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH bpf-next 2/3] bpf: use cgroup_{common,current}_func_proto in more hooks
Date: Sat, 13 Aug 2022 14:25:54 +0800 [thread overview]
Message-ID: <202208131415.CkdRZBrY-lkp@intel.com> (raw)
In-Reply-To: <20220812190241.3544528-3-sdf@google.com>
Hi Stanislav,
I love your patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Stanislav-Fomichev/bpf-expose-bpf_-g-s-et_retval-to-more-cgroup-hooks/20220813-030615
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: x86_64-randconfig-a013 (https://download.01.org/0day-ci/archive/20220813/202208131415.CkdRZBrY-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/0429824054f7a843ee976d48432e825e493a0a7e
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Stanislav-Fomichev/bpf-expose-bpf_-g-s-et_retval-to-more-cgroup-hooks/20220813-030615
git checkout 0429824054f7a843ee976d48432e825e493a0a7e
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/bpf/helpers.c: In function 'cgroup_current_func_proto':
>> kernel/bpf/helpers.c:1817:25: error: 'bpf_get_cgroup_classid_curr_proto' undeclared (first use in this function)
1817 | return &bpf_get_cgroup_classid_curr_proto;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
kernel/bpf/helpers.c:1817:25: note: each undeclared identifier is reported only once for each function it appears in
vim +/bpf_get_cgroup_classid_curr_proto +1817 kernel/bpf/helpers.c
1797
1798 /* Common helpers for cgroup hooks with valid process context. */
1799 const struct bpf_func_proto *
1800 cgroup_current_func_proto(enum bpf_func_id func_id, const struct bpf_prog *prog)
1801 {
1802 switch (func_id) {
1803 #ifdef CONFIG_CGROUPS
1804 case BPF_FUNC_get_current_uid_gid:
1805 return &bpf_get_current_uid_gid_proto;
1806 case BPF_FUNC_get_current_pid_tgid:
1807 return &bpf_get_current_pid_tgid_proto;
1808 case BPF_FUNC_get_current_comm:
1809 return &bpf_get_current_comm_proto;
1810 case BPF_FUNC_get_current_cgroup_id:
1811 return &bpf_get_current_cgroup_id_proto;
1812 case BPF_FUNC_get_current_ancestor_cgroup_id:
1813 return &bpf_get_current_ancestor_cgroup_id_proto;
1814 #endif
1815 #ifdef CONFIG_CGROUP_NET_CLASSID
1816 case BPF_FUNC_get_cgroup_classid:
> 1817 return &bpf_get_cgroup_classid_curr_proto;
1818 #endif
1819 default:
1820 return NULL;
1821 }
1822 }
1823
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-08-13 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 19:02 [PATCH bpf-next 0/3] bpf: expose bpf_{g,s}et_retval to more cgroup hooks Stanislav Fomichev
2022-08-12 19:02 ` [PATCH bpf-next 1/3] bpf: introduce cgroup_{common,current}_func_proto Stanislav Fomichev
2022-08-15 21:26 ` Martin KaFai Lau
2022-08-16 17:19 ` Stanislav Fomichev
2022-08-12 19:02 ` [PATCH bpf-next 2/3] bpf: use cgroup_{common,current}_func_proto in more hooks Stanislav Fomichev
2022-08-13 6:25 ` kernel test robot [this message]
2022-08-13 18:55 ` kernel test robot
2022-08-15 21:57 ` Martin KaFai Lau
2022-08-16 17:19 ` Stanislav Fomichev
2022-08-12 19:02 ` [PATCH bpf-next 3/3] selftests/bpf: make sure bpf_{g,s}et_retval is exposed everywhere Stanislav Fomichev
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=202208131415.CkdRZBrY-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@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;
as well as URLs for NNTP newsgroup(s).