From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755558AbaEEP5L (ORCPT ); Mon, 5 May 2014 11:57:11 -0400 Received: from mail-qa0-f46.google.com ([209.85.216.46]:53732 "EHLO mail-qa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754719AbaEEP5I (ORCPT ); Mon, 5 May 2014 11:57:08 -0400 X-Google-Original-From: Vince Weaver Date: Mon, 5 May 2014 12:00:44 -0400 (EDT) From: Vince Weaver To: Peter Zijlstra cc: Vince Weaver , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, Steven Rostedt Subject: Re: [perf] more perf_fuzzer memory corruption In-Reply-To: <20140505093124.GN17778@laptop.programming.kicks-ass.net> Message-ID: References: <20140502162234.GX11096@twins.programming.kicks-ass.net> <20140502172731.GK30445@twins.programming.kicks-ass.net> <20140505093124.GN17778@laptop.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 Mon, 5 May 2014, Peter Zijlstra wrote: > Does this one work better? Making sure all __perf_remove_from_context() > callers pass the right structure seems to improve things no end. My > machine is now happy to reboot again. Yes, I've been fuzzing this for a few hours on both my haswell and core2 test systems and it's doing great, also survived a reboot cycle. Tested-by: Vince Weaver (Although often things like to crash the instant my tested-by e-mails clear the lkml list.) I also want to say thanks for all the work everyone has done in getting this analyzed and fixed. Vince