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
Date: Tue, 5 Apr 2016 13:18:20 +0200 [thread overview]
Message-ID: <20160405111820.GK3448@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CACT4Y+b9=Y-BAEk9HrDRdny8nL_OArepJ1+6skUaYL8X=tjaBw@mail.gmail.com>
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?
next prev parent reply other threads:[~2016-04-05 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 13:02 lockdep WARNING in get_online_cpus Dmitry Vyukov
2016-04-04 8:19 ` Dmitry Vyukov
2016-04-04 9:01 ` Peter Zijlstra
2016-04-04 9:50 ` Dmitry Vyukov
2016-04-05 9:41 ` Peter Zijlstra
2016-04-05 9:44 ` Dmitry Vyukov
2016-04-05 11:18 ` Peter Zijlstra [this message]
2016-04-05 11:23 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160405111820.GK3448@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox