From: kbuild test robot <lkp@intel.com>
To: Topi Miettinen <toiwoton@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Topi Miettinen <toiwoton@gmail.com>,
Jonathan Corbet <corbet@lwn.net>, Tejun Heo <tj@kernel.org>,
Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Markus Elfring <elfring@users.sourceforge.net>,
"David S. Miller" <davem@davemloft.net>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list:CONTROL GROUP (CGROUP)" <cgroups@vger.kernel.org>
Subject: Re: [PATCH 02/14] resource limits: aggregate task highwater marks to cgroup level
Date: Fri, 15 Jul 2016 20:38:05 +0800 [thread overview]
Message-ID: <201607152035.HD6NrG08%fengguang.wu@intel.com> (raw)
In-Reply-To: <1468578983-28229-3-git-send-email-toiwoton@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]
Hi,
[auto build test ERROR on v4.7-rc7]
[also build test ERROR on next-20160715]
[cannot apply to tip/sched/core rdma/master]
[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/Topi-Miettinen/Present-useful-limits-to-user-v2/20160715-194333
config: i386-randconfig-s1-201628 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/cgroup.c: In function 'cgroup_update_stats_from_task':
>> kernel/cgroup.c:4681:12: error: 'struct cgroup' has no member named 'stats'
if (cgrp->stats.resource_hiwater[i] <
^~
>> kernel/cgroup.c:4682:11: error: 'struct signal_struct' has no member named 'resource_highwatermark'
sig->resource_highwatermark[i])
^~
kernel/cgroup.c:4683:9: error: 'struct cgroup' has no member named 'stats'
cgrp->stats.resource_hiwater[i] =
^~
kernel/cgroup.c:4684:9: error: 'struct signal_struct' has no member named 'resource_highwatermark'
sig->resource_highwatermark[i];
^~
kernel/cgroup.c: In function 'cgroupstats_build':
kernel/cgroup.c:4773:36: error: 'struct cgroup' has no member named 'stats'
stats->resource_hiwater[i] = cgrp->stats.resource_hiwater[i];
^~
vim +4681 kernel/cgroup.c
4675 /* Attempt a lockless read on the first round. */
4676 nextseq = 0;
4677 do {
4678 seq = nextseq;
4679 flags = read_seqbegin_or_lock_irqsave(&sig->stats_lock, &seq);
4680 for (i = 0; i < RLIM_NLIMITS; i++)
> 4681 if (cgrp->stats.resource_hiwater[i] <
> 4682 sig->resource_highwatermark[i])
4683 cgrp->stats.resource_hiwater[i] =
4684 sig->resource_highwatermark[i];
4685
---
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: 22648 bytes --]
next prev parent reply other threads:[~2016-07-15 12:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1468578983-28229-1-git-send-email-toiwoton@gmail.com>
2016-07-15 10:35 ` [PATCH 01/14] resource limits: foundation for resource highwater tracking Topi Miettinen
2016-07-15 12:12 ` kbuild test robot
2016-07-15 12:49 ` Nicolas Dichtel
2016-07-15 16:27 ` Topi Miettinen
2016-07-15 17:57 ` Nicolas Dichtel
2016-07-15 10:35 ` [PATCH 02/14] resource limits: aggregate task highwater marks to cgroup level Topi Miettinen
2016-07-15 12:38 ` kbuild test robot [this message]
2016-07-15 14:10 ` Tejun Heo
2016-07-15 17:15 ` Topi Miettinen
2016-07-18 22:52 ` Tejun Heo
2016-07-19 16:57 ` Topi Miettinen
2016-07-19 18:18 ` Tejun Heo
2016-07-15 10:35 ` [PATCH 03/14] resource limits: track highwater mark of file sizes Topi Miettinen
2016-07-15 10:35 ` [PATCH 04/14] resource limits: track highwater mark of VM data segment Topi Miettinen
2016-07-15 10:35 ` [PATCH 05/14] resource limits: track highwater mark of stack size Topi Miettinen
2016-07-15 10:35 ` [PATCH 06/14] resource limits: track highwater mark of cores dumped Topi Miettinen
2016-07-15 10:35 ` [PATCH 07/14] resource limits: track highwater mark of user processes Topi Miettinen
2016-07-15 10:35 ` [PATCH 08/14] resource limits: track highwater mark of number of files Topi Miettinen
2016-07-15 10:35 ` [PATCH 10/14] resource limits: track highwater mark of address space size Topi Miettinen
2016-07-15 10:35 ` [PATCH 11/14] resource limits: track highwater mark of number of pending signals Topi Miettinen
2016-07-15 10:35 ` [PATCH 12/14] resource limits: track highwater mark of size of message queues Topi Miettinen
2016-07-15 10:36 ` [PATCH 13/14] resource limits: track highwater mark of niceness Topi Miettinen
2016-07-15 10:36 ` [PATCH 14/14] resource limits: track highwater mark of RT priority Topi Miettinen
2016-07-15 17:42 ` [PATCH 00/14] Present useful limits to user (v2) Topi Miettinen
[not found] ` <20160715124330.GR30154@twins.programming.kicks-ass.net>
[not found] ` <28b4b919-4f50-d9f6-c5e1-d1e92ea1ba1c@gmail.com>
[not found] ` <20160715135956.GA3115@twins.programming.kicks-ass.net>
2016-07-15 20:54 ` H. Peter Anvin
2016-07-18 13:00 ` Austin S. Hemmelgarn
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=201607152035.HD6NrG08%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=elfring@users.sourceforge.net \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=nicolas.dichtel@6wind.com \
--cc=tj@kernel.org \
--cc=toiwoton@gmail.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
all inboxes | Powered by JetHome®