[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52A88AFB.7000204@oracle.com>
Date: Wed, 11 Dec 2013 10:55:39 -0500
From: Sasha Levin <sasha.levin@...cle.com>
To: Jiri Kosina <jkosina@...e.cz>
CC: Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>, joern@...fs.org,
mgorman@...e.de, Michel Lespinasse <walken@...gle.com>,
riel@...hat.com, LKML <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: kernel BUG in munlock_vma_pages_range
On 12/09/2013 04:16 PM, Jiri Kosina wrote:
> On Mon, 9 Dec 2013, Sasha Levin wrote:
>
>> Not really, the fuzzer hit it once and I've been unable to trigger it
>> again.
>
> If you are ever able to trigger it again, I think having crashdump
> available would be very helpful here, to see how exactly does the VMA/THP
> layout look like at the time of crash.
>
> Any chance you run your fuzzing with crashkernel configured for a while?
>
Been trying to, can't get crashkernel to interact nicely with my KVM tools guest.
Will keep trying.
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