Date: Wed, 28 Feb 2018 19:43:00 +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: Re: syzkaller for freebsd again Message-ID: <CACT4Y%2Bb=Yfd6B0oyfo%2BW1fc_GmKWu-LRvaiP_g_oBXaPXpDjPA@mail.gmail.com> In-Reply-To: <CAPyFy2C_vRj=4Sf7YmzPdwb7NbXXHqcAQ=S2_kEOHCbdG7mT%2Bg@mail.gmail.com> References: <CACT4Y%2BZuBeqvdVY4KXSvrHAMgRVxZkkB=Q0%2BPjTOXzXUg%2B3DeA@mail.gmail.com> <CAPyFy2C_vRj=4Sf7YmzPdwb7NbXXHqcAQ=S2_kEOHCbdG7mT%2Bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 28, 2018 at 3:38 AM, Ed Maste <emaste@freebsd.org> wrote: > On 21 December 2017 at 04:26, Dmitry Vyukov <dvyukov@google.com> wrote: >> >> 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 > > Hi Dmitry, > > Yes, I had one of my co-op students work on automation for setting up > and running Syzkaller (in this case, on Packet.net's infrastructure). > It's certainly still quite early for us; we hadn't yet done work on > Syzkaller itself for FreeBSD. > > I think the most important change for us to make effective use of > Syzkaller is going to be having kernel coverage support. I have two > new Waterloo co-op students for this Jan-Apr work term and one of them > is getting close to having a working kcov implementation; once this is > ready we'll pick up the execution again. Hi Ed, Yes, coverage would be great. Assuming that the kernel interface is not radically different from linux, changes on syzkaller side should be trivial. Ready to merge that when you are ready. >> 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 > > Thanks, we'll take a look at this too. The FreeBSD release engineering > team produces GCE images so much of the infrastructure exists already. > Right now it's only straightforward to build FreeBSD from FreeBSD, so > it might take some work to integrate this with the setup you describe > here. We could create another master VM with freebsd. Should not be a problem. Since all code is Go porting should be almost zero effort too. The syz-ci thing (which continuously builds kernels and images) can also run locally (using, say, qemu VMs for actual testing). So you could make it work locally first (which will be a useful thing in itself), and once that works, we can start looking at setting up real continuous testing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACT4Y%2Bb=Yfd6B0oyfo%2BW1fc_GmKWu-LRvaiP_g_oBXaPXpDjPA>