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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
