From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753147AbaEBULn (ORCPT ); Fri, 2 May 2014 16:11:43 -0400 Received: from mail-qa0-f42.google.com ([209.85.216.42]:39336 "EHLO mail-qa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753129AbaEBULl (ORCPT ); Fri, 2 May 2014 16:11:41 -0400 X-Google-Original-From: Vince Weaver Date: Fri, 2 May 2014 16:15:11 -0400 (EDT) From: Vince Weaver To: Thomas Gleixner cc: Vince Weaver , Peter Zijlstra , Ingo Molnar , linux-kernel@vger.kernel.org, Steven Rostedt Subject: Re: [perf] more perf_fuzzer memory corruption In-Reply-To: Message-ID: References: <20140501150948.GR11096@twins.programming.kicks-ass.net> <20140502154217.GW11096@twins.programming.kicks-ass.net> <20140502162234.GX11096@twins.programming.kicks-ass.net> <20140502172731.GK30445@twins.programming.kicks-ass.net> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2 May 2014, Thomas Gleixner wrote: > Hmm, and where comes the WARN_ON in _free_event() from? That's not in > Peters last patch. ahh, you're right :( My fault. I gave the new patch and the previous patch similar names and applied the wrong one. OK the proper patch has been running the quick reproducer for a bit without triggering the issue, I'll let it run a bit more and then upgrade to full fuzzing. Vince