From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [4.7+] various memory corruption reports.
Date: Fri, 29 Jul 2016 11:19:07 -0400 [thread overview]
Message-ID: <20160729151907.GC29545@codemonkey.org.uk> (raw)
In-Reply-To: <20160729150513.GB29545@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.
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [4.7+] various memory corruption reports.
Date: Fri, 29 Jul 2016 11:19:07 -0400 [thread overview]
Message-ID: <20160729151907.GC29545@codemonkey.org.uk> (raw)
In-Reply-To: <20160729150513.GB29545@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.
Dave
next prev parent reply other threads:[~2016-07-29 15:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 15:05 [4.7+] various memory corruption reports Dave Jones
2016-07-29 15:05 ` Dave Jones
2016-07-29 15:19 ` Dave Jones [this message]
2016-07-29 15:19 ` Dave Jones
2016-07-29 15:21 ` Andrey Ryabinin
2016-07-29 15:21 ` Andrey Ryabinin
2016-07-29 15:49 ` Dave Jones
2016-07-29 15:49 ` Dave Jones
2016-07-29 17:32 ` Andrey Ryabinin
2016-07-29 17:32 ` Andrey Ryabinin
2016-07-29 17:56 ` Andrey Ryabinin
2016-07-29 17:56 ` Andrey Ryabinin
2016-07-29 18:39 ` Dave Jones
2016-07-29 18:39 ` Dave Jones
2016-08-01 11:03 ` Andrey Ryabinin
2016-08-01 11:03 ` Andrey Ryabinin
2016-08-01 16:37 ` Dave Jones
2016-08-01 16:37 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160729151907.GC29545@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.