Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751474AbaDQOyq (ORCPT ); Thu, 17 Apr 2014 10:54:46 -0400 Received: from merlin.infradead.org ([205.233.59.134]:58036 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751370AbaDQOyZ (ORCPT ); Thu, 17 Apr 2014 10:54:25 -0400 Date: Thu, 17 Apr 2014 16:54:18 +0200 From: Peter Zijlstra To: Vince Weaver Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: [perf] more perf_fuzzer memory corruption Message-ID: <20140417145418.GM11096@twins.programming.kicks-ass.net> References: <20140416141514.GS11182@twins.programming.kicks-ass.net> <20140417094815.GA9348@gmail.com> <20140417114533.GJ11096@twins.programming.kicks-ass.net> <20140417142213.GA29338@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 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 17, 2014 at 10:42:47AM -0400, Vince Weaver wrote: > On Thu, 17 Apr 2014, Ingo Molnar wrote: > > > > > * 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." > > I have to admit the slab corruption message is a new development with > 3.15-rc1. Meh.. my machine keeps locking up with 15-rc1 and your fuzzer. It looks to get stuck a finish_task_switch() from a preemption while waiting for a perf IPI. Which is complete crack because we have preemption disabled over issueing and waiting for the IPI :/ I tried reverting some of the IPI related patches, but no joy so far, I'm about to go try a git-bisect on this. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/