From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: ARC-Seal: i=1; a=rsa-sha256; t=1516627945; cv=none; d=google.com; s=arc-20160816; b=o65JBOlDSQBhbejQZFSIvcUXv/BbTls8jyFnFcry06Z0ixQbQDMeacln+WAfnn/2yb wmejBiXTrdXoZGfWsVHGz4BSYBHYB7v904C+eXajUO623/FyL7Tt3TF/DnzVikM5Kq6U zU2og3tjhdMosxgGJCYXhbjr7QoLZoo74bclxtlKH2w6SnjFPNT1b67IRAnOV4YS3KLD aprJjZmdvwjXfJkcxhSbnxiaXjG6gU+DOFnJ42PCLhfHa2+SlKntFbQQbpz1+C7pznjk oZvLHSRrAsvCJie9dbANihSpyL9lcy6GT8YooEGsN4M8xJ6xwCIh2KtOcAznyPXiHA79 EFXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:dkim-signature:arc-authentication-results; bh=HaeYtgU4A71tlIKZRrsfytYe6rQDS6QqiCw69GaSyZI=; b=F7PUdEC5+8THkP/OZ31VJ1VtSNESgWw27PitUOLsr+uWIBwCNaMypuUNCASs6C44wo PdpVVu5KnEP9041I1hwlMSzYC1b5GAomsSGceZu4eDhNak7klcM+fTBPSLDdrqa3GoMG G+gvSkoqSUKRLG6JdFzKHmIwshc9YX3wqphTMu0nY4qWAvqsm7mtfwTO1hkMBGrrXsdd /6fCZcA6yZmwHRqvxag5+Qi3e5nsDegIChWogKlsgwqtw12xXF+rZ1Bc6GuVafgwD+ie uslD6lMcqHMMZvbkKPNOcYBXXKfADwHzz14V7Oy2dBn1VkxC63KGDs07HjaBezh2GF4x zo/Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=NISbdP/J; spf=pass (google.com: domain of dvyukov@google.com designates 209.85.220.41 as permitted sender) smtp.mailfrom=dvyukov@google.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=NISbdP/J; spf=pass (google.com: domain of dvyukov@google.com designates 209.85.220.41 as permitted sender) smtp.mailfrom=dvyukov@google.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com X-Google-Smtp-Source: AH8x224J33lukZMjcgkyrQryFRLa5OxVm90jiOSmQtURc3ImIDER12Bo80dWtXR4IThxJ7mN4hufakGJLctwi2tiT3Q= MIME-Version: 1.0 In-Reply-To: <20180116173440.GA15893@kroah.com> References: <873735n3dy.fsf@xmission.com> <20180116173440.GA15893@kroah.com> From: Dmitry Vyukov Date: Mon, 22 Jan 2018 14:32:04 +0100 Message-ID: Subject: Re: what trees/branches to test on syzbot To: Greg Kroah-Hartman Cc: "Eric W. Biederman" , Guenter Roeck , LKML , "Theodore Ts'o" , Andrew Morton , Linus Torvalds , syzkaller , Stephen Rothwell , David Miller , Fengguang Wu Content-Type: text/plain; charset="UTF-8" X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1589734662777833222?= X-GMAIL-MSGID: =?utf-8?q?1590299664937155234?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On Tue, Jan 16, 2018 at 6:34 PM, Greg Kroah-Hartman wrote: > On Tue, Jan 16, 2018 at 11:02:17AM -0600, Eric W. Biederman wrote: >> Dmitry Vyukov writes: >> >> > On Tue, Jan 16, 2018 at 10:45 AM, Guenter Roeck wrote: >> >> On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov wrote: >> >>> Hello, >> >>> >> >>> Several people proposed that linux-next should not be tested on >> >>> syzbot. While some people suggested that it needs to test as many >> >>> trees as possible. I've initially included linux-next as it is a >> >>> staging area before upstream tree, with the intention that patches are >> >>> _tested_ there, is they are not tested there, bugs enter upstream >> >>> tree. And then it takes much longer to get fix into other trees. >> >>> >> >>> So the question is: what trees/branches should be tested? Preferably >> >>> in priority order as syzbot can't test all of them. >> >>> >> >> >> >> I always thought that -next existed specifically to give people a >> >> chance to test the code in it. Maybe the question is where to report >> >> the test results ? >> > >> > FTR, from Guenter on another thread: >> > >> >> Interesting. Assuming that refers to linux-next, not linux-net, that >> >> may explain why linux-next tends to deteriorate. I wonder if I should >> >> drop it from my testing as well. I'll be happy to follow whatever the >> >> result of this exchange is and do the same. >> > >> > If we agree on some list of important branches, and what branches >> > specifically should not be tested with automatic reporting, I think it >> > will benefit everybody. >> > +Fengguang, can you please share your list and rationale behind it? >> >> The problem is testing linux-next and then using get-maintainer.pl to >> report the problem. >> >> If you are resource limited I would start by testing Linus's tree to >> find the existing bugs, and to get a baseline. Using get-maintainer.pl >> is fine for sending emails to developers there. > > I second this, almost all of the issues you are hitting are usually in > Linus's tree. Let's make that "clean" first, before messing around and > adding 100+ other random developer's trees into the mix :) FTR I've just dropped linux-next and mmots from syzbot.