[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160715075006.GN9806@techsingularity.net>
Date: Fri, 15 Jul 2016 08:50:06 +0100
From: Mel Gorman <mgorman@...hsingularity.net>
To: kernel test robot <xiaolong.ye@...el.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Michal Hocko <mhocko@...e.com>,
Hillf Danton <hillf.zj@...baba-inc.com>,
Johannes Weiner <hannes@...xchg.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Minchan Kim <minchan@...nel.org>,
Rik van Riel <riel@...riel.com>,
Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: Re: [lkp] [mm, memcg] 849400b8b0: WARNING: CPU: 0 PID: 1 at
mm/memcontrol.c:998 mem_cgroup_update_lru_size+0x220/0x297
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
Powered by blists - more mailing lists