From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752555AbaEGTM0 (ORCPT ); Wed, 7 May 2014 15:12:26 -0400 Received: from mail-ee0-f53.google.com ([74.125.83.53]:37412 "EHLO mail-ee0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750866AbaEGTMW (ORCPT ); Wed, 7 May 2014 15:12:22 -0400 Date: Wed, 7 May 2014 21:12:16 +0200 From: Ingo Molnar To: Vince Weaver Cc: Peter Zijlstra , Thomas Gleixner , linux-kernel@vger.kernel.org, Steven Rostedt , Arnaldo Carvalho de Melo , =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker Subject: Re: [perf] more perf_fuzzer memory corruption Message-ID: <20140507191216.GB23040@gmail.com> References: <20140505093124.GN17778@laptop.programming.kicks-ass.net> <20140505172951.GB7154@gmail.com> 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 Tue, 6 May 2014, Vince Weaver wrote: > > > In any case if we can get the recent patches applied in time for 3.15 I > > think it will turn out to be a nice release perf-event-stability wise. > > I should also mention I have a list of open perf_fuzzer issues here: > http://web.eece.maine.edu/~vweaver/projects/perf_events/fuzzer/bugs_found.html > > It's not organized well but it's how I keep track of the various issues > after I find and report them. That looks useful, thanks! Ingo