From: kernel test robot <lkp@intel.com>
To: Vasily Averin <vvs@virtuozzo.com>,
Pablo Neira Ayuso <pablo@netfilter.org>
Cc: kbuild-all@lists.01.org, netfilter-devel@vger.kernel.org,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>
Subject: Re: [PATCH] ipset: enable memory accounting for ipset allocations
Date: Fri, 25 Sep 2020 15:53:33 +0800 [thread overview]
Message-ID: <202009251545.3tm8FvXD%lkp@intel.com> (raw)
In-Reply-To: <f3cb80cc-523f-afa7-6ee2-7f06b68f4976@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]
Hi Vasily,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on nf/master]
[also build test ERROR on nf-next/master ipvs/master v5.9-rc6 next-20200924]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Vasily-Averin/ipset-enable-memory-accounting-for-ipset-allocations/20200925-135627
base: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git master
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/828ea197585b5e87760b3d5615b52919ab9a3b10
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Vasily-Averin/ipset-enable-memory-accounting-for-ipset-allocations/20200925-135627
git checkout 828ea197585b5e87760b3d5615b52919ab9a3b10
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
net/netfilter/ipset/ip_set_core.c: In function 'ip_set_alloc':
>> net/netfilter/ipset/ip_set_core.c:253:24: error: 'GFP_KERNEL_ALLOC' undeclared (first use in this function); did you mean 'GFP_KERNEL_ACCOUNT'?
253 | return kvzalloc(size, GFP_KERNEL_ALLOC);
| ^~~~~~~~~~~~~~~~
| GFP_KERNEL_ACCOUNT
net/netfilter/ipset/ip_set_core.c:253:24: note: each undeclared identifier is reported only once for each function it appears in
>> net/netfilter/ipset/ip_set_core.c:254:1: warning: control reaches end of non-void function [-Wreturn-type]
254 | }
| ^
vim +253 net/netfilter/ipset/ip_set_core.c
248
249 /* Utility functions */
250 void *
251 ip_set_alloc(size_t size)
252 {
> 253 return kvzalloc(size, GFP_KERNEL_ALLOC);
> 254 }
255 EXPORT_SYMBOL_GPL(ip_set_alloc);
256
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65077 bytes --]
next prev parent reply other threads:[~2020-09-25 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 5:55 [PATCH] ipset: enable memory accounting for ipset allocations Vasily Averin
2020-09-25 7:53 ` kernel test robot [this message]
2020-09-25 8:56 ` [PATCH v2] " Vasily Averin
2020-10-04 19:09 ` Pablo Neira Ayuso
2020-09-25 9:13 ` [PATCH] " kernel test robot
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=202009251545.3tm8FvXD%lkp@intel.com \
--to=lkp@intel.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kbuild-all@lists.01.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=vvs@virtuozzo.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).