Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1334505 > unrolled thread

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

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [RFC][PATCH 00/12] various perf fixes Dmitry Vyukov <dvyukov@google.com> - 2016-02-15 16:10 +0100
    Re: [RFC][PATCH 00/12] various perf fixes Peter Zijlstra <peterz@infradead.org> - 2016-02-15 16:50 +0100
      Re: [RFC][PATCH 00/12] various perf fixes Dmitry Vyukov <dvyukov@google.com> - 2016-02-15 16:50 +0100
      Re: [RFC][PATCH 00/12] various perf fixes Vince Weaver <vince@deater.net> - 2016-02-15 17:10 +0100

#1334505 — Re: [RFC][PATCH 00/12] various perf fixes

On Thu, Jan 14, 2016 at 11:05 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
> On Thu, Jan 14, 2016 at 10:35 AM, Peter Zijlstra <peterz@infradead.org> wrote:
>> On Tue, Jan 12, 2016 at 12:26:27PM +0100, Dmitry Vyukov wrote:
>>> What do you think if we work on making syzkaller work for you locally?
>>
>> There's no easy way to do this right? I had a look at that project on
>> github and it looks like the most complex test setup possible :-(
>>
>> I don't generally do VMs so I'm not much good at setting those up nor do
>> I speak Go (although I did play the game a lot of years ago).
>>
>> Isn't there an easy way to just run syz-fuzzer on a machine without all
>> the bells and whistles on?


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. Are there any existing bugs left that you know
about? Or should I report new crashes?
Did you have any luck setting up syzkaller locally? That could
significantly reduce turnaround time.



> 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
>
> Download syzkaller sources:
>
> $ go get github.com/google/syzkaller
>
> Build necessary syzkaller binaries:
>
> $ cd $GOPATH/src/github.com/google/syzkaller
> $ make
>
> Then save the following content into
> $GOPATH/src/github.com/google/syzkaller/perf.cfg
>
> {
>         "http": "localhost:50000",
>         "workdir": "home/gopath/src/github.com/google/syzkaller/workdir",
>         "syzkaller": "/home/gopath/src/github.com/google/syzkaller",
>         "vmlinux": "-",
>         "type": "local",
>         "count": 1,
>         "procs": 16,
>         "nocover": true,
>         "nodropprivs": true,
>         "enable_syscalls": [
>                 "getpid",
>                 "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.
>
> 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

[toc] | [next] | [standalone]

#1334546

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 :/

[toc] | [prev] | [next] | [standalone]

#1334550

On Mon, Feb 15, 2016 at 4:38 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> 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 :/

It should not be _too_ hard :)
Feel free to contact me or syzkaller@googlegroups.com if you have any
issues with setup.

[toc] | [prev] | [next] | [standalone]

#1334565

On Mon, 15 Feb 2016, Peter Zijlstra wrote:

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

I was glad to see the fixes go by, since a lot of the
syzkaller reports are very similar to open bugs I have with perf_fuzzer.

I have to admit I've been busy/lazy recently and so was waiting for the 
fixes to hit an actual Linus -rc kernel before ramping up my fuzz testing 
again.

Vince

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web