From owner-freebsd-hackers@freebsd.org Wed Feb 28 18:43:22 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A844CF3C414 for ; Wed, 28 Feb 2018 18:43:22 +0000 (UTC) (envelope-from dvyukov@google.com) Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3168687497 for ; Wed, 28 Feb 2018 18:43:22 +0000 (UTC) (envelope-from dvyukov@google.com) Received: by mail-pf0-x22d.google.com with SMTP id y186so1363858pfb.2 for ; Wed, 28 Feb 2018 10:43:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=t3gyz0jt+BdRixwh96i8WbuzrV+wIvmhiS9bz5mQkX8=; b=MA79FuknzhYWla2asooXhXnNCTuoX8fEYDGNJu3VPWw2JRJLdGvtojJ+4g0h2XplQg yPLzDknQEHMeoH8r50VHaONpFHBV3hfYGO+nGyP+y8w3MpMRUZjc4Yhvehy1UaemL55G fYEj2nT3PsrtYIaQ5dNTRclDQfkVsSU59nB8pr9RXV1ia6gb0z8hEFEykfFuJUz7Nfu6 xrqZpuowwp7mGJ5GAjH0oGpa8caKERe4A1aPR59aHv/tHyIbzDnEDMZP9UkVaGcwY2Wr 0vw2t7e3xRZ7IdsRezf8p8Lwf3wblgL9LF2tBQqJd4rmmSIIS4fjCHEK8odzdpoYGgST sRRw== X-Gm-Message-State: APf1xPDWk8kqKb5kKiHgl0HyQwtawmsweWiPN3yvtSTE3JUJnDj1/LEe yOVHgnZkZuKVNsjDIqI1OODP2uPtY/UO3gzk0/ryPg== X-Google-Smtp-Source: AH8x2254MMJDTy8vTUmprljFtSUEYDJhwf+0HQ1HjHX1P7+59SPGtr9sHehGWq5QH0plLavcKGlDh02ptVBzQivWoUs= X-Received: by 10.98.110.71 with SMTP id j68mr16837069pfc.93.1519843401073; Wed, 28 Feb 2018 10:43:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.140.151 with HTTP; Wed, 28 Feb 2018 10:43:00 -0800 (PST) In-Reply-To: References: From: Dmitry Vyukov Date: Wed, 28 Feb 2018 19:43:00 +0100 Message-ID: Subject: Re: syzkaller for freebsd again To: Ed Maste Cc: FreeBSD Hackers , syzkaller Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Wed, 28 Feb 2018 20:07:56 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2018 18:43:22 -0000 On Wed, Feb 28, 2018 at 3:38 AM, Ed Maste wrote: > On 21 December 2017 at 04:26, Dmitry Vyukov 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.