Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755623AbaDQJsc (ORCPT ); Thu, 17 Apr 2014 05:48:32 -0400 Received: from mail-ee0-f50.google.com ([74.125.83.50]:36528 "EHLO mail-ee0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755211AbaDQJsU (ORCPT ); Thu, 17 Apr 2014 05:48:20 -0400 Date: Thu, 17 Apr 2014 11:48:15 +0200 From: Ingo Molnar To: Vince Weaver Cc: Peter Zijlstra , linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: [perf] more perf_fuzzer memory corruption Message-ID: <20140417094815.GA9348@gmail.com> References: <20140416141514.GS11182@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Vince Weaver wrote: > On Wed, 16 Apr 2014, Vince Weaver wrote: > > > On Wed, 16 Apr 2014, Peter Zijlstra wrote: > > > > > Does the below make any difference? I've only ran it through some light > > > testing to make sure it didn't insta-explode on running. > > > > > > (perf stat make -j64 -s in fact) > > > > I'm running with your patch now and so far so good. > > spoke too soon, just got this with your patch applied > (I wasn't running ftrace so no trace with this one): Is there some place where I can pick up the latestest of your fuzzer? PeterZ has trouble reproducing the corruption locally - I'd like to run it too, maybe I have hardware that triggers it more readily. Plus it would be nice to get your latest .config as well, that you are using to generate this crash. (You can send it in private mail as well if you wish.) Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/