LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@kernel.org>, Dmitry Vyukov <dvyukov@google.com>
Cc: Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Lutomirski <luto@kernel.org>,
Ingo Molnar <mingo@redhat.com>, X86 ML <x86@kernel.org>
Subject: Re: general protection fault in syscall_return_slowpath
Date: Sun, 08 Mar 2020 19:26:22 +0100 [thread overview]
Message-ID: <87eeu28zzl.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CALCETrV7JcVt3ejMbHxTs4-CFmKjcmSbW2eMmmMZUM7dg2mBuA@mail.gmail.com>
Andy Lutomirski <luto@kernel.org> writes:
> On Sat, Mar 7, 2020 at 11:45 PM syzbot
> <syzbot+cd66e43794b178bb5cd6@syzkaller.appspotmail.com> wrote:
> $ make -j4
> tools/syz-env/env.go:14:2: cannot find package
> "github.com/google/syzkaller/pkg/osutil" in any of:
>
> I'm sure that if I actually understood Go's delightful packaging
> system, I could reverse engineer your build system and figure out how
> to make it work. But perhaps you could document the build process?
> Or maybe make 'make' just work?
>
> For kicks, I tried this:
>
> $ mkdir -p src/github.com/google
> $ ln -sr . src/github.com/google/syzkaller
> $ GOPATH=`/bin/pwd` make
> GOOS=linux GOARCH=amd64 go install ./syz-manager
> go install: no install location for directory
> /home/luto/apps/syzkaller/syz-manager outside GOPATH
>
> Are there instructions for just building syzkaller? I don't want to
> install it, I don't want to fuzz my kernel -- I just want to run your
> reproducer.
https://github.com/google/syzkaller/blob/master/docs/executing_syzkaller_programs.md
That's how I build the binaries:
mkdir foo
export GOPATH=$HOME/foo
cd foo
go get -u -d github.com/google/syzkaller/...
cd src/github.com/google/syzkaller
make
cp bin/linux_amd64/syz-execprog bin/linux_amd64/syz-executor $GOPATH
Of course you can build it somewhere and scp the executables to a test box.
And then to run it
cd $GOPATH
wget -O repro.syz https://syzkaller.appspot.com/x/repro.syz?x=12a42329e00000
./syz-execprog -procs 6 -repeat 0 -collide -disable none repro.syz
The command line options are a bit tedious as you have to look them up
in the comment in repro.syz.
A scripts which converts that comment into command line options or
syz-execprog simply taking it from repro.syz would indeed be handy.
A kernel with the config provided in the report and running that
reproducer is still not reproducing with a runtime of 8hrs+ :(
Thanks,
tglx
next prev parent reply other threads:[~2020-03-08 18:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 7:45 syzbot
2020-03-08 16:13 ` Andy Lutomirski
2020-03-08 16:37 ` Borislav Petkov
2020-03-08 18:26 ` Thomas Gleixner [this message]
2020-03-09 8:34 ` Dmitry Vyukov
2020-03-09 18:26 ` Eric Biggers
2020-03-10 5:41 ` Dmitry Vyukov
2020-03-09 8:42 ` Dmitry Vyukov
2020-03-08 16:29 ` Andy Lutomirski
2020-03-12 13:34 ` Dan Carpenter
2020-03-08 17:20 ` Jann Horn
2020-03-08 18:00 ` syzbot
2020-03-08 18:35 ` Jann Horn
2020-03-08 21:57 ` syzbot
2020-03-09 8:20 ` Dmitry Vyukov
2020-03-10 6:15 ` Nathan Chancellor
2020-03-10 8:10 ` Dmitry Vyukov
2020-06-14 8:03 ` Dmitry Vyukov
2020-06-15 7:57 ` Jann Horn
2020-08-15 10:18 ` syzbot
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=87eeu28zzl.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=x86@kernel.org \
--subject='Re: general protection fault in syscall_return_slowpath' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).