From: kbuild test robot <fengguang.wu@intel.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 7192/7206] mm/memcontrol.c:3017:9: error: implicit declaration of function 'memcg_online_kmem'
Date: Fri, 18 Dec 2015 21:16:55 +0800 [thread overview]
Message-ID: <201512182150.Ai69BCxz%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f7ac28a6971b43a2ee8bb47c0ef931b38f7888cf
commit: 7292b6db051d2fd307eeca4a1985868735927b0c [7192/7206] mm: memcontrol: reign in the CONFIG space madness
config: i386-randconfig-r0-201550 (attached as .config)
reproduce:
git checkout 7292b6db051d2fd307eeca4a1985868735927b0c
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
mm/memcontrol.c: In function 'memcg_update_kmem_limit':
>> mm/memcontrol.c:3017:9: error: implicit declaration of function 'memcg_online_kmem' [-Werror=implicit-function-declaration]
ret = memcg_online_kmem(memcg);
^
mm/memcontrol.c: In function 'mem_cgroup_can_attach':
mm/memcontrol.c:4880:9: warning: 'memcg' may be used uninitialized in this function [-Wmaybe-uninitialized]
mc.to = memcg;
^
cc1: some warnings being treated as errors
vim +/memcg_online_kmem +3017 mm/memcontrol.c
d6441637 Vladimir Davydov 2014-01-23 3011 {
b2878698 Johannes Weiner 2015-12-18 3012 int ret;
b2878698 Johannes Weiner 2015-12-18 3013
b2878698 Johannes Weiner 2015-12-18 3014 mutex_lock(&memcg_limit_mutex);
b2878698 Johannes Weiner 2015-12-18 3015 /* Top-level cgroup doesn't propagate from root */
b2878698 Johannes Weiner 2015-12-18 3016 if (!memcg_kmem_online(memcg)) {
b2878698 Johannes Weiner 2015-12-18 @3017 ret = memcg_online_kmem(memcg);
b2878698 Johannes Weiner 2015-12-18 3018 if (ret)
b2878698 Johannes Weiner 2015-12-18 3019 goto out;
d6441637 Vladimir Davydov 2014-01-23 3020 }
:::::: The code at line 3017 was first introduced by commit
:::::: b28786989bd0894d5e6e9fa0a8916973510666e8 mm: memcontrol: move kmem accounting code to CONFIG_MEMCG
:::::: TO: Johannes Weiner <hannes@cmpxchg.org>
:::::: CC: Stephen Rothwell <sfr@canb.auug.org.au>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 28258 bytes --]
reply other threads:[~2015-12-18 13:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201512182150.Ai69BCxz%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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