From: kbuild test robot <lkp@intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: kbuild-all@01.org, Eric Dumazet <edumazet@google.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net_sched: use kvmalloc rather than opencoded variant
Date: Sun, 15 Jan 2017 07:43:01 +0800 [thread overview]
Message-ID: <201701150720.coxUa02H%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170106160743.GU5556@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
Hi Michal,
[auto build test ERROR on net-next/master]
[also build test ERROR on v4.10-rc3 next-20170113]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Michal-Hocko/net_sched-use-kvmalloc-rather-than-opencoded-variant/20170107-120926
config: i386-randconfig-h1-01150559 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
net/sched/sch_fq.c: In function 'fq_resize':
>> net/sched/sch_fq.c:643:10: error: implicit declaration of function 'kvmalloc_node' [-Werror=implicit-function-declaration]
array = kvmalloc_node(sizeof(struct rb_root) << log, GFP_KERNEL | __GFP_REPEAT,
^~~~~~~~~~~~~
net/sched/sch_fq.c:643:8: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
array = kvmalloc_node(sizeof(struct rb_root) << log, GFP_KERNEL | __GFP_REPEAT,
^
cc1: some warnings being treated as errors
vim +/kvmalloc_node +643 net/sched/sch_fq.c
637 u32 idx;
638
639 if (q->fq_root && log == q->fq_trees_log)
640 return 0;
641
642 /* If XPS was setup, we can allocate memory on right NUMA node */
> 643 array = kvmalloc_node(sizeof(struct rb_root) << log, GFP_KERNEL | __GFP_REPEAT,
644 netdev_queue_numa_node_read(sch->dev_queue));
645 if (!array)
646 return -ENOMEM;
---
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: 30475 bytes --]
next prev parent reply other threads:[~2017-01-14 23:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 15:20 __GFP_REPEAT usage in fq_alloc_node Michal Hocko
2017-01-06 15:39 ` Eric Dumazet
2017-01-06 16:07 ` Michal Hocko
2017-01-06 16:19 ` Michal Hocko
2017-01-07 3:33 ` [PATCH] net: use kvmalloc rather than open coded variant kbuild test robot
2017-01-07 9:19 ` Michal Hocko
2017-01-07 3:35 ` kbuild test robot
2017-01-09 10:22 ` __GFP_REPEAT usage in fq_alloc_node Michal Hocko
2017-01-09 16:00 ` Eric Dumazet
2017-01-09 17:45 ` Michal Hocko
2017-01-09 17:53 ` Eric Dumazet
2017-01-14 23:43 ` kbuild test robot [this message]
2017-01-16 8:54 ` [PATCH] net_sched: use kvmalloc rather than opencoded variant Michal Hocko
2017-01-06 16:31 ` __GFP_REPEAT usage in fq_alloc_node Vlastimil Babka
2017-01-06 16:48 ` Eric Dumazet
2017-01-06 16:50 ` Eric Dumazet
2017-01-06 16:55 ` Vlastimil Babka
2017-01-06 17:08 ` Eric Dumazet
2017-01-06 17:18 ` Vlastimil Babka
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=201701150720.coxUa02H%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
/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).