Re: [4.7+] various memory corruption reports.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]