From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751023AbaECHd3 (ORCPT ); Sat, 3 May 2014 03:33:29 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:42938 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750875AbaECHd2 convert rfc822-to-8bit (ORCPT ); Sat, 3 May 2014 03:33:28 -0400 Date: Sat, 3 May 2014 09:33:14 +0200 From: Peter Zijlstra To: Vince Weaver Cc: Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, Steven Rostedt Subject: Re: [perf] more perf_fuzzer memory corruption Message-ID: <20140503073314.GJ17778@laptop.programming.kicks-ass.net> References: <20140502162234.GX11096@twins.programming.kicks-ass.net> <20140502172731.GK30445@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 02, 2014 at 11:02:25PM -0400, Vince Weaver wrote: > On Fri, 2 May 2014, Vince Weaver wrote: > > > I've been fuzzing without your additional patch for 6 hours and all looks > > (almost) good. I can add in your patch and let it fuzz overnight. > > and I applied the additional patch, installed the kernel, hit reboot, and > the following happened (this was caused by rebooting while fuzzing > was ongoing) :( > > I'm remote from the system too so the poor machine is going to be sitting > there oopsing away until Monday. Yeah, my system did the same when I tried to shut it down last night. I have remote power though (or else I would've been forced to like walk downstairs) :-) I suppose that means I'll have something to do come Monday morning.