Re: [4.7+] various memory corruption reports.

From	Dave Jones <davej@codemonkey.org.uk>
Newsgroups	linux.kernel
Subject	Re: [4.7+] various memory corruption reports.
Date	2016-07-29 17:50 +0200
Message-ID	<s0icW-6y2-19@gated-at.bofh.it> (permalink)
References	<s0hAe-6iI-23@gated-at.bofh.it> <s0hJT-6nB-11@gated-at.bofh.it> <s0hTz-6qP-11@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, Jul 29, 2016 at 06:21:12PM +0300, Andrey Ryabinin wrote:
 > 2016-07-29 18:19 GMT+03:00 Dave Jones <davej@codemonkey.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

Thread

Re: [4.7+] various memory corruption reports. Dave Jones <davej@codemonkey.org.uk> - 2016-07-29 17:20 +0200
  Re: [4.7+] various memory corruption reports. Andrey Ryabinin <ryabinin.a.a@gmail.com> - 2016-07-29 17:30 +0200
    Re: [4.7+] various memory corruption reports. Dave Jones <davej@codemonkey.org.uk> - 2016-07-29 17:50 +0200
      Re: [4.7+] various memory corruption reports. Andrey Ryabinin <ryabinin.a.a@gmail.com> - 2016-07-29 19:40 +0200
        Re: [4.7+] various memory corruption reports. Andrey Ryabinin <ryabinin.a.a@gmail.com> - 2016-07-29 20:00 +0200
          Re: [4.7+] various memory corruption reports. Dave Jones <davej@codemonkey.org.uk> - 2016-07-29 20:40 +0200
            Re: [4.7+] various memory corruption reports. Andrey Ryabinin <ryabinin.a.a@gmail.com> - 2016-08-01 14:10 +0200
              Re: [4.7+] various memory corruption reports. Dave Jones <davej@codemonkey.org.uk> - 2016-08-01 19:30 +0200

csiph-web