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 S1757880AbcDELSZ (ORCPT <rfc822;w@1wt.eu>);
	Tue, 5 Apr 2016 07:18:25 -0400
Received: from casper.infradead.org ([85.118.1.10]:60303 "EHLO
	casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756369AbcDELSY (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 5 Apr 2016 07:18:24 -0400
Date: Tue, 5 Apr 2016 13:18:20 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>, "x86@kernel.org" <x86@kernel.org>,
        LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
        Oleg Nesterov <oleg@redhat.com>,
        syzkaller <syzkaller@googlegroups.com>,
        Kostya Serebryany <kcc@google.com>,
        Alexander Potapenko <glider@google.com>,
        Sasha Levin <sasha.levin@oracle.com>
Subject: Re: lockdep WARNING in get_online_cpus
Message-ID: <20160405111820.GK3448@twins.programming.kicks-ass.net>
References: <CACT4Y+a82mMqLh+faQAhvPs28xMkm_ezyAm9O3r5JzynDpKK4w@mail.gmail.com>
 <CACT4Y+YO6DNEPB5BD7G4hw07XbYCZ=4v4QyR9su1jpOEQPNeEg@mail.gmail.com>
 <20160404090143.GW3448@twins.programming.kicks-ass.net>
 <CACT4Y+Z0AwBceU0NxDTSkAFf=TiiVdY1cJjvZ1KUb8DYwdGk-A@mail.gmail.com>
 <20160405094134.GJ3448@twins.programming.kicks-ass.net>
 <CACT4Y+b9=Y-BAEk9HrDRdny8nL_OArepJ1+6skUaYL8X=tjaBw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACT4Y+b9=Y-BAEk9HrDRdny8nL_OArepJ1+6skUaYL8X=tjaBw@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 Tue, Apr 05, 2016 at 11:44:13AM +0200, Dmitry Vyukov wrote:
> On Tue, Apr 5, 2016 at 11:41 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Mon, Apr 04, 2016 at 11:50:07AM +0200, Dmitry Vyukov wrote:
> >> Yes, I am able to reproduce it by running:
> >>
> >> # ./syz-execprog  -cover=0 -repeat=0 -procs=20 -nobody=0
> >> crash-qemu-26-1459761514194788294
> >>
> >> crash-qemu-26-1459761514194788294 being:
> >> https://gist.githubusercontent.com/dvyukov/bce719c2b7dede54f96d8bbb7c78714f/raw/08a7a237986f0e3bccc7c0e800a3bdaa32e1fc0b/gistfile1.txt
> >
> >
> > root@ivb-ep:~/gopath/src/github.com/google/syzkaller# ./bin/syz-execprog -cover=0 -repeat=0 -procs=20 -nobody=0 gistfile1.txt
> > 2016/04/05 11:39:37 parsed 391 programs
> > 2016/04/05 11:39:37 executed 0 programs
> > result: failed=false hanged=false err=failed to start executor binary: fork/exec /root/gopath/src/github.com/google/syzkaller: permission denied
> >
> > result: failed=false hanged=false err=failed to start executor binary: fork/exec /root/gopath/src/github.com/google/syzkaller: permission denied
> >
> > result: failed=false hanged=false err=failed to start executor binary: fork/exec /root/gopath/src/github.com/google/syzkaller: permission denied
> >
> > (which goes on ad inf.)
> >
> > Clearly I'm not doing it right.. help?
> 
> The latest version of syz-execproc uses ./syz-executor by default. If
> you don't have ./syz-executor, add -executor=/path/to/syz-executor.

I still have the version you helped make work; I saw that the config
file format had changed since so I've not updated because I didn't want
borkage.

In any case, that did indeed work. But it doesn't trigger the collision
for me :/

I'm running a fairly bloated (distro derived) .config with various debug
options (including lockdep and lockdep_debug) enabled.

Should I maybe do a 'normal' fuzz run to see if that will trigger it? I
need a config for that though, as I only have the perf specific one.
Also, how likely is running this thing as root on bare metal going to
wreck things?