From: kbuild test robot <lkp@intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: kbuild-all@01.org, Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tobias Klauser <tklauser@distanz.ch>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] mm, vmalloc: fix vmalloc users tracking properly
Date: Tue, 9 May 2017 23:59:55 +0800 [thread overview]
Message-ID: <201705092345.OV9tGwwX%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170509144108.31910-1-mhocko@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 5270 bytes --]
Hi Michal,
[auto build test ERROR on mmotm/master]
[also build test ERROR on next-20170509]
[cannot apply to v4.11]
[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/mm-vmalloc-fix-vmalloc-users-tracking-properly/20170509-224536
base: git://git.cmpxchg.org/linux-mmotm.git master
config: c6x-evmc6678_defconfig (attached as .config)
compiler: c6x-elf-gcc (GCC) 6.2.0
reproduce:
wget https://raw.githubusercontent.com/01org/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=c6x
All errors (new ones prefixed by >>):
mm/nommu.c:51:5: sparse: symbol 'sysctl_nr_trim_pages' was not declared. Should it be static?
mm/nommu.c:52:5: sparse: symbol 'heap_stack_gap' was not declared. Should it be static?
mm/nommu.c:63:35: sparse: symbol 'generic_file_vm_ops' was not declared. Should it be static?
mm/nommu.c:240:6: sparse: symbol '__vmalloc_node_flags' was not declared. Should it be static?
mm/nommu.c:1175:48: sparse: incorrect type in argument 2 (different address spaces)
mm/nommu.c:1175:48: expected char [noderef] <asn:1>*<noident>
mm/nommu.c:1175:48: got void *[assigned] base
mm/nommu.c:1790:15: sparse: symbol 'arch_get_unmapped_area' was not declared. Should it be static?
mm/nommu.c:638:9: sparse: context imbalance in '__put_nommu_region' - wrong count at exit
mm/nommu.c:659:13: sparse: context imbalance in 'put_nommu_region' - unexpected unlock
In file included from include/asm-generic/io.h:767:0,
from ./arch/c6x/include/generated/asm/io.h:1,
from include/linux/io.h:25,
from include/linux/irq.h:24,
from include/asm-generic/hardirq.h:12,
from arch/c6x/include/asm/hardirq.h:18,
from include/linux/hardirq.h:8,
from include/linux/memcontrol.h:24,
from include/linux/swap.h:8,
from mm/nommu.c:23:
include/linux/vmalloc.h:85:21: error: conflicting types for '__vmalloc_node_flags_caller'
static inline void *__vmalloc_node_flags_caller(unsigned long size, int node, gfp_t flags, void* caller)
^~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/vmalloc.h:84:14: note: previous declaration of '__vmalloc_node_flags_caller' was here
extern void *__vmalloc_node_flags_caller(unsigned long size, int node, gfp_t flags);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/vmalloc.h: In function '__vmalloc_node_flags_caller':
include/linux/vmalloc.h:87:9: error: implicit declaration of function '__vmalloc_node_flags' [-Werror=implicit-function-declaration]
return __vmalloc_node_flags(size, node, flags);
^~~~~~~~~~~~~~~~~~~~
include/linux/vmalloc.h:87:9: warning: return makes pointer from integer without a cast [-Wint-conversion]
return __vmalloc_node_flags(size, node, flags);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mm/nommu.c: At top level:
>> mm/nommu.c:240:7: error: conflicting types for '__vmalloc_node_flags'
void *__vmalloc_node_flags(unsigned long size, int node, gfp_t flags)
^~~~~~~~~~~~~~~~~~~~
In file included from include/asm-generic/io.h:767:0,
from ./arch/c6x/include/generated/asm/io.h:1,
from include/linux/io.h:25,
from include/linux/irq.h:24,
from include/asm-generic/hardirq.h:12,
from arch/c6x/include/asm/hardirq.h:18,
from include/linux/hardirq.h:8,
from include/linux/memcontrol.h:24,
from include/linux/swap.h:8,
from mm/nommu.c:23:
include/linux/vmalloc.h:87:9: note: previous implicit declaration of '__vmalloc_node_flags' was here
return __vmalloc_node_flags(size, node, flags);
^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/__vmalloc_node_flags +240 mm/nommu.c
8518609d Robert P. J. Day 2007-10-19 234 * returns only a logical address.
^1da177e Linus Torvalds 2005-04-16 235 */
84097518 Nick Piggin 2006-03-22 236 return kmalloc(size, (gfp_mask | __GFP_COMP) & ~__GFP_HIGHMEM);
^1da177e Linus Torvalds 2005-04-16 237 }
b5073173 Paul Mundt 2007-07-21 238 EXPORT_SYMBOL(__vmalloc);
^1da177e Linus Torvalds 2005-04-16 239
c7e6abdb Michal Hocko 2017-05-03 @240 void *__vmalloc_node_flags(unsigned long size, int node, gfp_t flags)
c7e6abdb Michal Hocko 2017-05-03 241 {
c7e6abdb Michal Hocko 2017-05-03 242 return __vmalloc(size, flags, PAGE_KERNEL);
c7e6abdb Michal Hocko 2017-05-03 243 }
:::::: The code at line 240 was first introduced by commit
:::::: c7e6abdbe12a86cfa1bdba2bd3e9f5fdb1cb175b mm: introduce kv[mz]alloc helpers
:::::: TO: Michal Hocko <mhocko@suse.com>
:::::: CC: Johannes Weiner <hannes@cmpxchg.org>
---
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: 5454 bytes --]
next prev parent reply other threads:[~2017-05-09 16:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 14:41 [PATCH] mm, vmalloc: fix vmalloc users tracking properly Michal Hocko
2017-05-09 14:41 ` Michal Hocko
2017-05-09 14:51 ` Tobias Klauser
2017-05-09 14:51 ` Tobias Klauser
2017-05-09 15:25 ` kbuild test robot
2017-05-09 15:37 ` Michal Hocko
2017-05-09 15:37 ` Michal Hocko
2017-05-10 9:37 ` Geert Uytterhoeven
2017-05-10 9:37 ` Geert Uytterhoeven
2017-05-10 9:51 ` Tobias Klauser
2017-05-10 9:51 ` Tobias Klauser
2017-05-09 15:59 ` kbuild test robot [this message]
2017-05-09 19:01 ` Geert Uytterhoeven
2017-05-09 19:01 ` Geert Uytterhoeven
2017-05-09 19:36 ` Michal Hocko
2017-05-09 19:36 ` Michal Hocko
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=201705092345.OV9tGwwX%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=tklauser@distanz.ch \
--cc=torvalds@linux-foundation.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 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.