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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160729154929.GA30611@codemonkey.org.uk>
Date:	Fri, 29 Jul 2016 11:49:29 -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 Fri, Jul 29, 2016 at 06:21:12PM +0300, Andrey Ryabinin wrote:
 > 2016-07-29 18:19 GMT+03:00 Dave Jones <davej@...emonkey.org.uk>:
 > > On Fri, Jul 29, 2016 at 11:05:14AM -0400, Dave Jones wrote:
 > >  > I've just gotten back into running trinity on daily pulls of master, and it seems pretty horrific
 > >  > right now.  I can reproduce some kind of memory corruption within a couple minutes runtime.
 > >  >
 > >  > ,,,
 > >  >
 > >  > I'll work on narrowing down the exact syscalls needed to trigger this.
 > >
 > > Even limiting it to do just a simple syscall like execve (which fails most the time in trinity)
 > > triggers it, suggesting it's not syscall related, but the fact that trinity is forking/killing
 > > tons of processes at high rate is stressing something more fundamental.
 > >
 > > Given how easy this reproduces, I'll see if bisecting gives up something useful.
 > 
 > 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.

	Dave