From: kernel test robot <lkp@intel.com>
To: Anton Protopopov <aspsk@isovalent.com>, bpf@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Anton Protopopov <aspsk@isovalent.com>,
Joe Stringer <joe@isovalent.com>,
John Fastabend <john.fastabend@gmail.com>
Subject: Re: [PATCH bpf-next 1/2] bpf: add new map ops ->map_pressure
Date: Thu, 1 Jun 2023 08:44:24 +0800 [thread overview]
Message-ID: <202306010837.mGhA199K-lkp@intel.com> (raw)
In-Reply-To: <20230531110511.64612-2-aspsk@isovalent.com>
Hi Anton,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Anton-Protopopov/bpf-add-new-map-ops-map_pressure/20230531-190704
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20230531110511.64612-2-aspsk%40isovalent.com
patch subject: [PATCH bpf-next 1/2] bpf: add new map ops ->map_pressure
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20230601/202306010837.mGhA199K-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.3.0
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/025cc7c86c6c7e108ba5b9946a0f50e0cc082f9b
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Anton-Protopopov/bpf-add-new-map-ops-map_pressure/20230531-190704
git checkout 025cc7c86c6c7e108ba5b9946a0f50e0cc082f9b
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=sh olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=sh SHELL=/bin/bash kernel/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306010837.mGhA199K-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/bpf/hashtab.c: In function 'htab_map_pressure':
>> kernel/bpf/hashtab.c:189:24: error: implicit declaration of function '__percpu_counter_sum'; did you mean 'percpu_counter_sum'? [-Werror=implicit-function-declaration]
189 | return __percpu_counter_sum(&htab->pcount);
| ^~~~~~~~~~~~~~~~~~~~
| percpu_counter_sum
cc1: some warnings being treated as errors
vim +189 kernel/bpf/hashtab.c
183
184 static u32 htab_map_pressure(const struct bpf_map *map)
185 {
186 struct bpf_htab *htab = container_of(map, struct bpf_htab, map);
187
188 if (htab->use_percpu_counter)
> 189 return __percpu_counter_sum(&htab->pcount);
190 return atomic_read(&htab->count);
191 }
192
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-01 0:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 11:05 [PATCH bpf-next 0/2] add mechanism to report map pressure Anton Protopopov
2023-05-31 11:05 ` [PATCH bpf-next 1/2] bpf: add new map ops ->map_pressure Anton Protopopov
2023-05-31 18:24 ` Alexei Starovoitov
2023-06-01 7:31 ` Anton Protopopov
2023-06-01 16:39 ` Alexei Starovoitov
2023-06-01 18:18 ` Anton Protopopov
2023-06-01 18:24 ` Alexei Starovoitov
2023-06-02 0:40 ` Alexei Starovoitov
2023-06-02 14:21 ` Anton Protopopov
2023-06-02 16:23 ` Alexei Starovoitov
2023-06-06 7:49 ` Anton Protopopov
2023-06-24 0:00 ` John Fastabend
2023-06-26 16:29 ` Anton Protopopov
2023-06-28 13:17 ` Anton Protopopov
2023-06-01 0:44 ` kernel test robot [this message]
2023-06-01 7:50 ` Anton Protopopov
2023-06-13 8:23 ` Yujie Liu
2023-06-13 8:30 ` Anton Protopopov
2023-05-31 11:05 ` [PATCH bpf-next 2/2] selftests/bpf: test map pressure Anton Protopopov
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=202306010837.mGhA199K-lkp@intel.com \
--to=lkp@intel.com \
--cc=aspsk@isovalent.com \
--cc=bpf@vger.kernel.org \
--cc=joe@isovalent.com \
--cc=john.fastabend@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.