linux-kernel - Re: [RFC][PATCH 00/12] various perf fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+bK64NAmVcbSSQWg1aC-=+3sjXsTd98pUqbd1JC92m=5w@mail.gmail.com>
Date:	Mon, 15 Feb 2016 17:35:51 +0100
From:	Dmitry Vyukov <dvyukov@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
	Stephane Eranian <eranian@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>, vince@...ter.net,
	Andi Kleen <andi@...stfloor.org>, jolsa@...hat.com,
	Thomas Gleixner <tglx@...utronix.de>,
	Arnaldo Carvalho de Melo <acme@...radead.org>
Subject: Re: [RFC][PATCH 00/12] various perf fixes

On Mon, Feb 15, 2016 at 5:29 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Thu, Jan 14, 2016 at 11:05:50AM +0100, Dmitry Vyukov wrote:
>> There is a way to run it without coverage on a local machine.
>>
>> First, you need to setup Go toolchain: download latest Go distribution
>> from https://golang.org/dl:
>> https://storage.googleapis.com/golang/go1.5.3.linux-amd64.tar.gz
>> Unpack it to $HOME/go1.5.
>>
>> $ export GOROOT=$HOME/go1.5
>
>> $ export GOPATH=$HOME/gopath
>
> So after I put that in a profile.d file:
>
>> Download syzkaller sources:
>>
>> $ go get github.com/google/syzkaller
>
> package github.com/google/syzkaller: no buildable Go source files in /root/gopath/src/github.com/google/syzkaller
>
>> Build necessary syzkaller binaries:
>>
>> $ cd $GOPATH/src/github.com/google/syzkaller
>> $ make
>
> That seems to have done its thing
>
>> Then save the following content into
>> $GOPATH/src/github.com/google/syzkaller/perf.cfg
>>
>
> {
>         "http": "localhost:50000",
>         "workdir": "root/gopath/src/github.com/google/syzkaller/workdir",
>         "syzkaller": "/root/gopath/src/github.com/google/syzkaller",
>         "vmlinux": "-",
>         "type": "local",
>         "count": 1,
>         "procs": 160,
>         "nocover": true,
>         "nodropprivs": true,
>         "enable_syscalls": [
>                 "perf_event_open",
>                 "ioctl$PERF*",
>                 "prctl$void",
>                 "bpf$*",
>                 "sched_yield"
>         ]
> }
>
>> Alter paths as necessary. Also you can change procs parameter (number
>> of parallel test processes), something like NCPU*4 would be a good
>> number. Also you can add additional syscalls to the mix.
>
> per the above
>
>> Then run:
>>
>> $ bin/syz-manager -config perf.cfg
>>
>> If you run it on a separate test machine, then scp syzkaller/bin dir
>> and perf.cfg to the machine (the syzkaller param in config is where it
>> will search for the bin dir).
>>
>> If syz-manager does not appear to be doing anything useful, then pleas
>> run it in the following mode and post output:
>>
>> $ bin/syz-manager -config perf.cfg -v 1 -debug
>
> root@...-ep:~/gopath/src/github.com/google/syzkaller# bin/syz-manager -config perf.cfg -v 1 -debug
> 2016/02/15 17:12:50 bad config syzkaller param: can't find bin/syz-execprog
>
> And its right, no such thing as bin/syz-execprog


Please also do:

$ make execprog

And replace:

        "nocover": true,
        "nodropprivs": true,

in config file with:

        "cover": false,
        "dropprivs": false,

(that's changed since I wrote the instructions).