From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751394AbaDQOWe (ORCPT ); Thu, 17 Apr 2014 10:22:34 -0400 Received: from mail-ee0-f50.google.com ([74.125.83.50]:60126 "EHLO mail-ee0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751465AbaDQOWS (ORCPT ); Thu, 17 Apr 2014 10:22:18 -0400 Date: Thu, 17 Apr 2014 16:22:13 +0200 From: Ingo Molnar To: Peter Zijlstra Cc: Vince Weaver , linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: [perf] more perf_fuzzer memory corruption Message-ID: <20140417142213.GA29338@gmail.com> References: <20140416141514.GS11182@twins.programming.kicks-ass.net> <20140417094815.GA9348@gmail.com> <20140417114533.GJ11096@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140417114533.GJ11096@twins.programming.kicks-ass.net> 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 * Peter Zijlstra wrote: > On Thu, Apr 17, 2014 at 11:48:15AM +0200, Ingo Molnar wrote: > > 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. > > From a few emails up: > > "If you want to try running the fuzzer on your machine too just do: > git clone https://github.com/deater/perf_event_tests.git > cd fuzzer > make > and then try running the "./fast_repro98.sh" script, as that's the forking > workload I've been using when tracking this issue." Cool, thanks! Ingo