Re: [4.7+] various memory corruption reports.

From: Dave Jones
Date: Mon Aug 01 2016 - 13:21:40 EST


On Mon, Aug 01, 2016 at 02:03:15PM +0300, Andrey Ryabinin wrote:
> On 07/29/2016 09:39 PM, Dave Jones wrote:
> > On Fri, Jul 29, 2016 at 08:56:08PM +0300, Andrey Ryabinin wrote:
> >
> > > >> > I suspect this is false positives due to changes in KASAN.
> > > >> > Bisection probably will point to
> > > >> > 80a9201a5965f4715d5c09790862e0df84ce0614 ("mm, kasan: switch SLUB to
> > > >> > stackdepot, enable memory quarantine for SLUB)"
> > > >>
> > > >> good call. reverting that changeset seems to have solved it.
> > > > Could you please try with this?
> > > Actually, this is not quite right, it should be like this:
> >
> >
> > Seems to have stopped the corruption, but now I get NMi watchdog traces..
> >
>
> This should help:

Yep, this seems to have silenced all the problems I saw.

thanks,

Dave