[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1606101253090.28031@nanos>
Date: Fri, 10 Jun 2016 14:54:59 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Dmitry Vyukov <dvyukov@...gle.com>
cc: Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
"x86@...nel.org" <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Konstantin Khlebnikov <koct9i@...il.com>,
syzkaller <syzkaller@...glegroups.com>,
Kostya Serebryany <kcc@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Sasha Levin <sasha.levin@...cle.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: x86: bad pte in pageattr_test
On Fri, 10 Jun 2016, Dmitry Vyukov wrote:
> Here is the second log:
> https://gist.githubusercontent.com/dvyukov/dd7970a5daaa7a30f6d37fa5592b56de/raw/f29182024538e604c95d989f7b398816c3c595dc/gistfile1.txt
>
> I've hit only twice. The first time I tried hard to reproduce it, with
> no success. So unfortunately that's all we have.
>
> Re logs: my setup executes up to 16 programs in parallel. So for
> normal BUGs any of the preceding 16 programs can be guilty. But since
> this check is asynchronous, it can be just any preceding program in
> the log.
Ok.
> I would expect that it is triggered by some rarely-executing poorly
> tested code. Maybe mmap of some device?
That's the mmap(dev) list which is common between the two log files:
vcsn
ircomm
rfkill
userio
dspn
mice
midi
sndpcmc
hidraw0
vga_arbiter
lightnvm
sr
Dunno, if that's the right direction, but exposing these a bit more might be
worth to try.
Thanks,
tglx
Powered by blists - more mailing lists