From: Dave Jones <davej@redhat.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Hugh Dickins <hughd@google.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Bob Liu <bob.liu@oracle.com>,
Konstantin Khlebnikov <koct9i@gmail.com>
Subject: Re: bad rss-counter message in 3.14rc5
Date: Tue, 18 Mar 2014 22:06:02 -0400 [thread overview]
Message-ID: <20140319020602.GA29787@redhat.com> (raw)
In-Reply-To: <5328F3B4.1080208@oracle.com>
On Tue, Mar 18, 2014 at 09:32:36PM -0400, Sasha Levin wrote:
> > Untested patch below: I can't quite say Reported-by, because it may
> > not even be one that you and Sasha have been seeing; but I'm hopeful,
> > remap_file_pages is in the list.
> >
> > Please give this a try, preferably on 3.14-rc or earlier: I've never
> > seen "Bad rss-counter"s there myself (trinity uses remap_file_pages
> > a lot more than most of us); but have seen them on mmotm/next, so
> > some other trigger is coming up there, I'll worry about that once
> > it reaches 3.15-rc.
>
> The patch fixed the "Bad rss-counter" errors I've been seeing both in
> 3.14-rc7 and -next.
It's looking good here too so far. I'll leave it running overnight to be sure.
Dave
--
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>
next prev parent reply other threads:[~2014-03-19 2:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 17:45 bad rss-counter message in 3.14rc5 Dave Jones
2014-03-05 17:57 ` Dave Jones
2014-03-07 0:22 ` Dave Jones
2014-03-11 2:49 ` Dave Jones
2014-03-11 3:13 ` Andrew Morton
2014-03-11 4:46 ` Andrew Morton
2014-03-11 4:50 ` Dave Jones
2014-03-11 4:51 ` Dave Jones
2014-03-11 5:01 ` Andrew Morton
2014-03-11 5:07 ` Dave Jones
2014-03-11 5:30 ` Dave Jones
2014-03-11 12:55 ` Sasha Levin
2014-03-11 13:20 ` Cyrill Gorcunov
2014-03-11 13:23 ` Sasha Levin
2014-03-11 13:41 ` Cyrill Gorcunov
2014-03-11 14:28 ` Dave Jones
2014-03-11 14:37 ` Cyrill Gorcunov
2014-03-11 14:58 ` Sasha Levin
2014-03-11 17:10 ` Dave Jones
2014-03-11 17:36 ` Cyrill Gorcunov
2014-03-11 17:39 ` Dave Jones
2014-03-14 12:27 ` Cyrill Gorcunov
2014-03-19 0:38 ` Hugh Dickins
2014-03-19 1:10 ` Linus Torvalds
2014-03-19 2:06 ` Hugh Dickins
2014-03-19 2:24 ` Linus Torvalds
2014-03-19 2:37 ` Hugh Dickins
2014-03-19 2:57 ` Linus Torvalds
2014-03-19 11:04 ` Jan Kara
2014-03-19 1:32 ` Sasha Levin
2014-03-19 2:06 ` Dave Jones [this message]
2014-03-19 2:11 ` Dave Jones
2014-03-19 2:19 ` Hugh Dickins
2014-03-19 14:52 ` Dave Jones
2014-03-20 5:00 ` Hugh Dickins
2014-03-20 13:51 ` Dave Jones
2014-03-20 14:19 ` Sasha Levin
2014-03-21 4:46 ` Hugh Dickins
2014-03-19 2:12 ` Hugh Dickins
2014-03-19 2:42 ` Sasha Levin
2014-03-19 12:04 ` Cyrill Gorcunov
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=20140319020602.GA29787@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=gorcunov@gmail.com \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).