From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: Sasha Levin <sasha.levin@oracle.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, 11 Mar 2014 18:37:50 +0400 [thread overview]
Message-ID: <20140311143750.GE32390@moon> (raw)
In-Reply-To: <20140311142817.GA26517@redhat.com>
On Tue, Mar 11, 2014 at 10:28:17AM -0400, Dave Jones wrote:
> On Tue, Mar 11, 2014 at 05:41:58PM +0400, Cyrill Gorcunov wrote:
> > On Tue, Mar 11, 2014 at 09:23:05AM -0400, Sasha Levin wrote:
> > > >>
> > > >>Ok, with move_pages excluded it still oopses.
> > > >
> > > >Dave, is it possible to somehow figure out was someone reading pagemap file
> > > >at moment of the bug triggering?
> > >
> > > We can sprinkle printk()s wherever might be useful, might not be 100% accurate but
> > > should be close enough to confirm/deny the theory.
> >
> > After reading some more, I suppose the idea I had is wrong, investigating.
> > Will ping if I find something.
>
> I can rule it out anyway, I can reproduce this by telling trinity to do nothing
> other than mmap()'s. I'll try and narrow down the exact parameters.
Dave, iirc trinity can write log file pointing which exactly syscall sequence
was passed, right? Share it too please.
next prev parent reply other threads:[~2014-03-11 14:37 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 [this message]
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
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=20140311143750.GE32390@moon \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=davej@redhat.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