From: Mel Gorman <mgorman@techsingularity.net>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Michal Hocko <mhocko@suse.com>,
Hillf Danton <hillf.zj@alibaba-inc.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Minchan Kim <minchan@kernel.org>, Rik van Riel <riel@surriel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp] [mm, memcg] 849400b8b0: WARNING: CPU: 0 PID: 1 at mm/memcontrol.c:998 mem_cgroup_update_lru_size+0x220/0x297
Date: Fri, 15 Jul 2016 08:50:06 +0100 [thread overview]
Message-ID: <20160715075006.GN9806@techsingularity.net> (raw)
In-Reply-To: <20160715014918.GA6978@yexl-desktop>
On Fri, Jul 15, 2016 at 09:49:18AM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 849400b8b0dfec6b7a681d62f45ade0a85858e46 ("mm, memcg: move memcg limit enforcement from zones to nodes")
>
Thanks. This one is known and a candidate patch has been tested by
Minchan. A follow-up series is in progress.
--
Mel Gorman
SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@techsingularity.net>
To: lkp@lists.01.org
Subject: Re: [mm, memcg] 849400b8b0: WARNING: CPU: 0 PID: 1 at mm/memcontrol.c:998 mem_cgroup_update_lru_size+0x220/0x297
Date: Fri, 15 Jul 2016 08:50:06 +0100 [thread overview]
Message-ID: <20160715075006.GN9806@techsingularity.net> (raw)
In-Reply-To: <20160715014918.GA6978@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Fri, Jul 15, 2016 at 09:49:18AM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 849400b8b0dfec6b7a681d62f45ade0a85858e46 ("mm, memcg: move memcg limit enforcement from zones to nodes")
>
Thanks. This one is known and a candidate patch has been tested by
Minchan. A follow-up series is in progress.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2016-07-15 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 1:49 [lkp] [mm, memcg] 849400b8b0: WARNING: CPU: 0 PID: 1 at mm/memcontrol.c:998 mem_cgroup_update_lru_size+0x220/0x297 kernel test robot
2016-07-15 1:49 ` kernel test robot
2016-07-15 7:50 ` Mel Gorman [this message]
2016-07-15 7:50 ` Mel Gorman
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=20160715075006.GN9806@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=riel@surriel.com \
--cc=sfr@canb.auug.org.au \
--cc=vbabka@suse.cz \
--cc=xiaolong.ye@intel.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 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.