Received: by 10.223.148.5 with SMTP id 5csp7411468wrq; Thu, 18 Jan 2018 05:14:15 -0800 (PST) X-Google-Smtp-Source: ACJfBos1ohqc2SjKchtBmZj6k2il81wpFQAjVV+DKshscNRnue4q8cNZ/9W7izYlUBJEoE3Edomb X-Received: by 10.99.148.26 with SMTP id m26mr36116874pge.157.1516281255600; Thu, 18 Jan 2018 05:14:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516281255; cv=none; d=google.com; s=arc-20160816; b=g+yCqIwl/FLkod8m36MKSHVoR1/gA9Mg/gvMzFyiyEBJDR3EYj2TvutsDAzmhGaOcc fhPP586UJV9QyC4H0Jd92QKHeWrq0Dpz6I5V0FguHptkUxsDpXwQY552Z2q/Qg/2eQL7 ZHcrkaZW11qqBApNCDzXzmJrUXQa74yroD6rU2eze5/oQvXxXdBdvJDWhmhi8wF6cfXw Rm8Q5jHZY60gIvbtVQy4Ax/jpeitld4WLrqQLpRC55kTOUAsbNdgUQ90FcQYq2onJCJn NfQwiD9cOqP5JakWttPceV+/o1O+btR+3BF4Abne87q8mHme5MDYlKnQNkxAdn+hSFRq B4mQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=5rFZs4YktcoYBnshRnAuXNmwcjLwJAgqE6xjEwjPr6E=; b=zBEthsPsR2H7BqKglzOCuqv54RPlGLk5jihgUbxIXBSlR72G1kjmfaUs0CANG+FF0O 5x6B0BjJqrpbUMnXVnxXlOGpRZmQJoUWQCdFLT/DUzBCrwFqLjl5rBBAGn0Al3eGnD3j ip25xbDPF2C1fW+0S9w0HDMy+BT7Eov7m9H4tt932OWnXrqNAQ9po/iYUPo0BLvx4Yv5 aCsPYa6w0d7M8IWp0qqbg20BZ3BbuK6lZdkQSJPjKfTPREsRjO6MVKXU55rMQaBvYZ7g Rx3wqDtF3LLGePcwmukJQnBrkUEKJic9lCi5a4XX9G5BEkD7u8hnKzeX0p9lOCmOO40C KcWw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=tV5qNpI3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b17si6644347pfd.406.2018.01.18.05.14.00; Thu, 18 Jan 2018 05:14:15 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=tV5qNpI3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756079AbeARNLB (ORCPT + 99 others); Thu, 18 Jan 2018 08:11:01 -0500 Received: from mail-pg0-f43.google.com ([74.125.83.43]:35954 "EHLO mail-pg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754998AbeARNK7 (ORCPT ); Thu, 18 Jan 2018 08:10:59 -0500 Received: by mail-pg0-f43.google.com with SMTP id k68so6505205pga.3 for ; Thu, 18 Jan 2018 05:10:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5rFZs4YktcoYBnshRnAuXNmwcjLwJAgqE6xjEwjPr6E=; b=tV5qNpI3Dg6+J5/p/A9XE/0P0UNAR+bSY1Y1C+0OPafA11KUXvsNl/ks5x3zzksMsi NqhAdoJHEV6idZaQR36yB23UrluiSn9CoqLsq1l5RHDdiWCEZS+HrEkNfuoJS9sg2icG 3R5Xz1hM8ZRFyPJW8WohyCz7NNbyk2JNZCqg0Ov/0mmd34EeZxGM/5eba/WNj18QpayB N+0Wi8F6WQE4ho7l5eUHNOUdP+Ina0HlumGGnMmAMA05rZxuzxb6FC7sFuGi9w16FN3s 654X0b96YYrz9EU4IIuNmBAYE2Vtewbnz4Gu9KPcdDPAaKO823wQ03B7KbEcgT5UeG4B BHkQ== 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=5rFZs4YktcoYBnshRnAuXNmwcjLwJAgqE6xjEwjPr6E=; b=TLxHm5j6n2aZnL2IqeDrGqQHoL4UuvZktISSAy+ujthj1Az14ECnMN8Ierzms3tah8 nVIrNaL3U9utEExF1LgsQ2SXFI1Qakf9gHIBINkg3qg/aCz6Cv2x73DTDWfIEIDLqH25 QSDo6QuQrSI5w1VV/+3neCD7Pb+wD38KIi6Fnn4X44CiZ92JXAe9Vja6xfaZ30IZNKo7 gSloYNJcH6Y4rwQzzcv/VEgyFTaPi6QFF1pyw7nckbzZw+jJaFc6kVGNewwVMprgRWCo TmNbi+RIl/138IroE+seoUDZzfdgarvYJEM4R4BbeISfMvOBTbLp8Ix/fj3UjNkVYRsk fOpw== X-Gm-Message-State: AKGB3mJ7Kyi2txrp1eYUsrjpz758lXbOSvD1N9p6AUkRw/52NBIfP2BA Q5cRDfo78+q+HMqlr59JbdCJUCRtX8cDYujd8a1aUQ== X-Received: by 10.99.126.86 with SMTP id o22mr32852779pgn.364.1516281058788; Thu, 18 Jan 2018 05:10:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.140.151 with HTTP; Thu, 18 Jan 2018 05:10:38 -0800 (PST) In-Reply-To: References: <001a11405130ff1e9705629eb53c@google.com> <20180117093225.GB20303@amd> From: Dmitry Vyukov Date: Thu, 18 Jan 2018 14:10:38 +0100 Message-ID: Subject: Re: dangers of bots on the mailing lists was Re: divide error in ___bpf_prog_run To: Daniel Borkmann , Alexei Starovoitov Cc: syzbot , Alexei Starovoitov , LKML , netdev Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 17, 2018 at 12:09 PM, Dmitry Vyukov wrote: > On Wed, Jan 17, 2018 at 10:49 AM, Daniel Borkmann wrote: >> Don't know if there's such a possibility, but it would be nice if we could >> target fuzzing for specific subsystems in related subtrees directly (e.g. >> for bpf in bpf and bpf-next trees as one example). Dmitry? > > Hi Daniel, > > It's doable. > Let's start with one bpf tree. Will it be bpf or bpf-next? Which one > contains more ongoing work? What's the exact git repo address/branch, > so that I don't second guess? > Also what syscalls it makes sense to enable there to target it at bpf > specifically? As far as I understand effects of bpf are far beyond the > bpf call and proper testing requires some sockets and other stuff. For > sockets, will it be enough to enable ip/ipv6? Because if we enable all > of sctp/dccp/tipc/pptp/etc, it will sure will be finding lots of bugs > there as well. Does bpf affect incoming network packets? > Also are there any sysctl's, command line arguments, etc that need to > be tuned. I know there are net.core.bpf_jit_enable/harden, but I don't > know what's the most relevant combination. Ideally, we test all of > them, but let start with one of them because it requires separate > instances (since the setting is global and test programs can't just > flip it randomly). > Also do you want testing from root or not from root? We generally > don't test under root, because syzkaller comes up with legal ways to > shut everything down even if we try to contain it (e.g. kill init > somehow or shut down network using netlink). But if we limit syscall > surface, then root may work and allow testing staging bpf features. So, Daniel, Alexei, I understand that I asked lots of questions, but they are relatively simple. I need that info to setup proper testing.