From: kbuild test robot <lkp@intel.com>
To: Roman Gushchin <guro@fb.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6841/7780] mm/memcontrol.c:5682:30: error: 'CGRP_GROUP_OOM' undeclared
Date: Fri, 20 Jul 2018 01:45:31 +0800 [thread overview]
Message-ID: <201807200126.ABKoOkoA%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1c34981993da96711f8c7037e0391df7daa33df9
commit: f5180e2e08ede6f4901788fa6335295acd0a0112 [6841/7780] mm, oom: return error on access to memory.oom_group if groupoom is disabled
config: x86_64-randconfig-ne0-07171435 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
git checkout f5180e2e08ede6f4901788fa6335295acd0a0112
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-next/master HEAD 1c34981993da96711f8c7037e0391df7daa33df9 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
mm/memcontrol.c: In function 'memory_oom_group_show':
>> mm/memcontrol.c:5682:30: error: 'CGRP_GROUP_OOM' undeclared (first use in this function)
if (!(cgrp_dfl_root.flags & CGRP_GROUP_OOM))
^~~~~~~~~~~~~~
mm/memcontrol.c:5682:30: note: each undeclared identifier is reported only once for each function it appears in
mm/memcontrol.c: In function 'memory_oom_group_write':
mm/memcontrol.c:5698:30: error: 'CGRP_GROUP_OOM' undeclared (first use in this function)
if (!(cgrp_dfl_root.flags & CGRP_GROUP_OOM))
^~~~~~~~~~~~~~
vim +/CGRP_GROUP_OOM +5682 mm/memcontrol.c
5676
5677 static int memory_oom_group_show(struct seq_file *m, void *v)
5678 {
5679 struct mem_cgroup *memcg = mem_cgroup_from_css(seq_css(m));
5680 bool oom_group = memcg->oom_group;
5681
> 5682 if (!(cgrp_dfl_root.flags & CGRP_GROUP_OOM))
5683 return -ENOTSUPP;
5684
5685 seq_printf(m, "%d\n", oom_group);
5686
5687 return 0;
5688 }
5689
---
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: 32761 bytes --]
reply other threads:[~2018-07-19 17:46 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=201807200126.ABKoOkoA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--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