linux-kernel - Re: [4.7+] various memory corruption reports.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160801163731.xmlcb7vi2hfqe3ri@codemonkey.org.uk>
Date:	Mon, 1 Aug 2016 12:37:31 -0400
From:	Dave Jones <davej@...emonkey.org.uk>
To:	Andrey Ryabinin <ryabinin.a.a@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [4.7+] various memory corruption reports.

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