From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754559Ab3E3Mqc (ORCPT ); Thu, 30 May 2013 08:46:32 -0400 Received: from mail-qc0-f170.google.com ([209.85.216.170]:54947 "EHLO mail-qc0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752877Ab3E3MqX (ORCPT ); Thu, 30 May 2013 08:46:23 -0400 Date: Thu, 30 May 2013 08:51:00 -0400 (EDT) From: Vince Weaver To: Peter Zijlstra cc: Vince Weaver , Al Viro , linux-kernel@vger.kernel.org, Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo , trinity@vger.kernel.org Subject: Re: OOPS in perf_mmap_close() In-Reply-To: <20130530072532.GF4341@laptop> Message-ID: References: <20130523044803.GA25399@ZenIV.linux.org.uk> <20130523125218.GB23650@twins.programming.kicks-ass.net> <20130523152611.GE23650@twins.programming.kicks-ass.net> <20130528085548.GA12193@twins.programming.kicks-ass.net> <20130529074433.GB12193@twins.programming.kicks-ass.net> <20130530072532.GF4341@laptop> 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 Thu, 30 May 2013, Peter Zijlstra wrote: > > Awesome! How specific is it to perf? I mean, would that tool work > equally well for other tinity report? No, it's fairly specific to my perf_fuzzer. I only use trinity code to set up the perf_event_open() attr parameters, everything else I use my own code for. The logging output from perf_fuzzer is fairly straightforward. Just a single char indicating which syscall and a space separated list of the result (if relevant) and then all the syscall parameters. The logging output can then be used by both the replayer and the sample-code generator. While in theory this could be extended to something generic, currently it only works for perf_event_open/close/ioctl/read/write/mmap/munmap, and even then it takes some shortcuts because I know it will only be run when finding perf_event problems. The code for all of this is here if anyone else wants to play with it. https://github.com/deater/perf_event_tests/tree/master/fuzzer > I'll go prod, thanks again! The bug looks related to hw breakpoints, not sure if the bugs Oleg Nesterov has been reporting in this area might be relevant or not. Vince