From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752050AbcBOPle (ORCPT <rfc822;w@1wt.eu>);
	Mon, 15 Feb 2016 10:41:34 -0500
Received: from [198.137.202.9] ([198.137.202.9]:40319 "EHLO
	bombadil.infradead.org" rhost-flags-FAIL-FAIL-OK-OK)
	by vger.kernel.org with ESMTP id S1751576AbcBOPlc (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 15 Feb 2016 10:41:32 -0500
Date: Mon, 15 Feb 2016 16:38:25 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Ingo Molnar <mingo@kernel.org>,
        Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        Stephane Eranian <eranian@google.com>,
        LKML <linux-kernel@vger.kernel.org>, vince@deater.net,
        Andi Kleen <andi@firstfloor.org>, jolsa@redhat.com,
        Thomas Gleixner <tglx@linutronix.de>,
        Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [RFC][PATCH 00/12] various perf fixes
Message-ID: <20160215153825.GH6357@twins.programming.kicks-ass.net>
References: <20160111162458.427203780@infradead.org>
 <20160112101109.GC20997@gmail.com>
 <CACT4Y+Zb4VE5HiAvEubFU6W=+iXgoDB-1xCSd_r3MYGzbetMxQ@mail.gmail.com>
 <CACT4Y+bNJi8T031hgbh832f1G9cKofYDx8maH6zSS93KnUQJLw@mail.gmail.com>
 <CACT4Y+Zdn2i0bG3=ALRkm2_RwAJE9WTf9qYb=5vXfDtos8Hzgg@mail.gmail.com>
 <CACT4Y+bAqP78kMGG3QxNUEEVCqesW8PhpL5KS+8U8=D0C4F71A@mail.gmail.com>
 <20160114093529.GU6344@twins.programming.kicks-ass.net>
 <CACT4Y+Ym0TZLkmRrM0ZGgLpu8kqS-YjoWTMrvaLz=tx2tnyO3w@mail.gmail.com>
 <CACT4Y+YoLo=ny6cJMrD8U68KouPNVz+pujYg_MJj+4BvTp0ZtQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACT4Y+YoLo=ny6cJMrD8U68KouPNVz+pujYg_MJj+4BvTp0ZtQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2012-12-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Feb 15, 2016 at 04:04:36PM +0100, Dmitry Vyukov wrote:
> Peter, I want to check status of these perf crashes. I see that you
> landed a bunch of patches. But I still see perf-related crashes while
> running syzkaller.

Bugger :-)

> Are there any existing bugs left that you know
> about? 

I might have one report, but I've been ill the past two weeks, so I'm
not too sure on that.

> Or should I report new crashes?

Please.

> Did you have any luck setting up syzkaller locally? That could
> significantly reduce turnaround time.

Not yet :/ I managed to reproduce a lot of fail with Vince's perf-fuzzer
and some stress test scripts Ingo had.

I suppose I'll have to go look at making this happen; right bugger for
requiring a weird language though :/