From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752976AbcG2PTO (ORCPT ); Fri, 29 Jul 2016 11:19:14 -0400 Received: from arcturus.aphlor.org ([188.246.204.175]:44242 "EHLO arcturus.aphlor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751551AbcG2PTL (ORCPT ); Fri, 29 Jul 2016 11:19:11 -0400 Date: Fri, 29 Jul 2016 11:19:07 -0400 From: Dave Jones To: Linux Kernel , Linus Torvalds , linux-mm@kvack.org Subject: Re: [4.7+] various memory corruption reports. Message-ID: <20160729151907.GC29545@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Linux Kernel , Linus Torvalds , linux-mm@kvack.org References: <20160729150513.GB29545@codemonkey.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160729150513.GB29545@codemonkey.org.uk> User-Agent: Mutt/1.6.0 (2016-04-01) X-Spam-Flag: skipped (authorised relay user) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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