linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKP <lkp@01.org>
Subject: Re: [   25.666092] WARNING: CPU: 0 PID: 451 at mm/memcontrol.c:998 mem_cgroup_update_lru_size
Date: Tue, 2 Aug 2016 09:22:43 +0100	[thread overview]
Message-ID: <20160802082243.GE2693@suse.de> (raw)
In-Reply-To: <20160801013830.GB27998@wfg-t540p.sh.intel.com>

On Mon, Aug 01, 2016 at 09:38:30AM +0800, Fengguang Wu wrote:
> Greetings,
> 
> 0day kernel testing robot got the below dmesg and the first bad commit is
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git mm-vmscan-node-lru-follow-up-v2r1
> 
> commit d5d54a2c5517f0818ad75a2f5b1d26a0dacae46a
> Author:     Mel Gorman <mgorman@techsingularity.net>
> AuthorDate: Wed Jul 13 09:30:01 2016 +0100
> Commit:     Mel Gorman <mgorman@techsingularity.net>
> CommitDate: Wed Jul 13 09:30:01 2016 +0100
> 

That bug is addressed later in the tree by "mm, vmscan: Update all zone
LRU sizes before updating memcg". Is the warning visible in the latest
mainline tree?

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-08-02  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01  1:38 Fengguang Wu
2016-08-02  8:22 ` Mel Gorman [this message]
2016-08-02 12:48   ` Fengguang Wu

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=20160802082243.GE2693@suse.de \
    --to=mgorman@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@01.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