From: David Ahern <dsahern@gmail.com>
To: William Tu <u9012063@gmail.com>
Cc: syzbot <syzbot+9723f2d288e49b492cf0@syzkaller.appspotmail.com>,
David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
linux-kernel@vger.kernel.org,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Subject: Re: KASAN: slab-out-of-bounds Read in erspan_xmit
Date: Tue, 23 Jan 2018 11:58:56 -0700 [thread overview]
Message-ID: <32f1adea-f2e3-9f29-bb1b-1b2116f13903@gmail.com> (raw)
In-Reply-To: <CALDO+SYScmeUsG5fqngNAuYAZZbPjkfFERKHuKgry_r+W194SA@mail.gmail.com>
On 1/23/18 11:50 AM, William Tu wrote:
> Hi,
>
> I'm new to kasan and trying to follow this instruction to reproduce the issue:
> https://github.com/google/syzkaller/blob/master/docs/executing_syzkaller_programs.md
>
> After re-compile my kernel with KASAN related config enable, I run
> $ ./syz-execprog -cover=0 -repeat=0 -procs=16 program
>
> I wonder does the "program" mean the repro.c.txt? or I should compile
> it to binary?
> # gcc -o program repro.c.txt
> # ./syz-execprog myprogram
> 2018/01/23 10:45:19 parsed 0 programs
>
> And how to use the "repro.syz.txt"?
> It seems to have some command like "syz_emit_ethernet" to generate packet.
> but I have no clue where to run it. Maybe I'm still missing something?
>
In the past I have only compiled a kernel with KASAN, compiled the
reproducer program and run it in a VM. No need for the syzbot overhead.
next prev parent reply other threads:[~2018-01-23 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 19:58 syzbot
2018-01-22 22:45 ` David Ahern
2018-01-22 22:57 ` William Tu
2018-01-23 18:50 ` William Tu
2018-01-23 18:58 ` David Ahern [this message]
2018-01-23 19:03 ` Dmitry Vyukov
2018-01-23 19:17 ` William Tu
2018-01-23 19:45 ` Dmitry Vyukov
2018-01-23 23:54 ` William Tu
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=32f1adea-f2e3-9f29-bb1b-1b2116f13903@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+9723f2d288e49b492cf0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=u9012063@gmail.com \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®