Date: Thu, 21 Dec 2017 10:26:26 +0100 From: Dmitry Vyukov <dvyukov@google.com> To: Ed Maste <emaste@freebsd.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, syzkaller <syzkaller@googlegroups.com> Subject: syzkaller for freebsd again Message-ID: <CACT4Y%2BZuBeqvdVY4KXSvrHAMgRVxZkkB=Q0%2BPjTOXzXUg%2B3DeA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi Ed, I see that you are using syzkaller and I've seen syzkaller mentioned in some frebsd announce. Do you mind sharing how extensively you are using it and how many bugs you have found? I wanted to point out that freebsd support in syzkaller is still far from being complete. We still need better descriptions of system calls and kernel code coverage, report parsing need improvements as well. For linux we are now finding 100+ bugs per months in a completely automated fashion using syzbot system: https://groups.google.com/forum/#!forum/syzkaller-bugs https://github.com/google/syzkaller/blob/master/docs/syzbot.md which does continuous building, fuzzing, automatic aggregation, reporting and status tracking. We could setup a similar thing for freebsd, but for that we need support for building freebsd kernel and GCE-compatible images. For linux that code lives here: https://github.com/google/syzkaller/blob/master/pkg/kernel/kernel.go https://github.com/google/syzkaller/blob/master/pkg/kernel/generated.go I don't know how size of freebsd kernel compares to linux, but if you don't measure bugs in hundreds, no, syzkaller is not yet working :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACT4Y%2BZuBeqvdVY4KXSvrHAMgRVxZkkB=Q0%2BPjTOXzXUg%2B3DeA>