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 S1751391AbcBOQTI (ORCPT <rfc822;w@1wt.eu>);
	Mon, 15 Feb 2016 11:19:08 -0500
Received: from [198.137.202.9] ([198.137.202.9]:41335 "EHLO
	bombadil.infradead.org" rhost-flags-FAIL-FAIL-OK-OK)
	by vger.kernel.org with ESMTP id S1751024AbcBOQTH (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 15 Feb 2016 11:19:07 -0500
Date: Mon, 15 Feb 2016 17:17:24 +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: <20160215161724.GI6357@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACT4Y+Ym0TZLkmRrM0ZGgLpu8kqS-YjoWTMrvaLz=tx2tnyO3w@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 Thu, Jan 14, 2016 at 11:05:50AM +0100, Dmitry Vyukov 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?
> 
> 
> 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.

I used: apt-get -t testing install golang, which gets me that same 1.5.3
version of Go (and I still think its a board game!).

> $ export GOROOT=$HOME/go1.5
> $ export GOPATH=$HOME/gopath

Fully expecting not to need nonsense like that.

> Download syzkaller sources:
> 
> $ go get github.com/google/syzkaller

But that yields:

~# go get github.com/google/syzkaller
package github.com/google/syzkaller: cannot download, $GOPATH not set.  For more details see: go help gopath

Clearly this stuff isn't meant to be used :/ Why doesn't it set a system
GOPATH in profile.d or whatnot. Why do I, as a user, need to be bothered
with crap like this.