[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <531F24A6.2020409@oracle.com>
Date: Tue, 11 Mar 2014 10:58:46 -0400
From: Sasha Levin <sasha.levin@...cle.com>
To: Cyrill Gorcunov <gorcunov@...il.com>, Dave Jones <davej@...hat.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-mm@...ck.org, Linus Torvalds <torvalds@...ux-foundation.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Bob Liu <bob.liu@...cle.com>,
Konstantin Khlebnikov <koct9i@...il.com>
Subject: Re: bad rss-counter message in 3.14rc5
On 03/11/2014 10:37 AM, Cyrill Gorcunov wrote:
> 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.
I've sent one of those last time I reported this issue:
https://lkml.org/lkml/2014/1/22/625
Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists