Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2548676imm; Sat, 9 Jun 2018 18:52:00 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJJ4U05tDrza2xmcqpoRFklTS7DZAV4hpOKztkwM2TPSsCQvDfuooxlpOyqwpBDi8T7iatN X-Received: by 2002:a62:da59:: with SMTP id w25-v6mr12001864pfl.161.1528595520538; Sat, 09 Jun 2018 18:52:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528595520; cv=none; d=google.com; s=arc-20160816; b=y5CIxhjDlzeaH03kL6BpBzFpIHQxHwTwqjmnu31sDP+VEIP4Lzf34rcC2Kgqt6p1dv XUkkwt5zHn81qXBq9i8wUZ6qtAFPPWrlW6YdM9c+JGsPXHXoG5V/B6DqZZI59KjDhpSw mCH3ogdbwwL3cEZnRkmHCSLqVS74BYTI207hw+Manm2H9QIxHdRwLdOdnyWQg6Ta9exF +msJXzSx7vMirVAtk6s7SdZVRJQFs8AZDXjDjCh/mJw4ywUJwz61FskpM6KqF4uQDdGF vp1JlSAR7ABGNT+rWuE+Z5PjUnFN6/0oeNtiSz6v8EUUOvkcEcr18im42qz/5PPBCwXi 7e+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=wdxLkN0gVRdrEWsrzryhWI3REiFOulFMro7XdrCMGew=; b=uX7nyW5W8gTW042rAKPsmrxwo1H6VVX+LOQrunHUYGnUjt12tI8x1Mc6KyXR4JEr1C q/kmTuunsq8Ickbxmoj1nc0JXQcl9yemP3Pg7Y+/ZepbT2q/orUbe/fnCZ6hEtc8SLiT OLu6Na/37nUZ199Mlzqm858Y+HYXrKjJnXZ4DY9cqWji1jKm4E9eZ08qP8g5bzm5kemM 5wvrFl5/kSoHcDRkoFaHm8VrP26JxEy6Rm9OixR7jhaSAzokt2YoXRl1WWixExOxQ8Cq Tt1Byi7cmngJlC90W/QAVnMvFUbf9R4Vy2a/ZoiKCcKRMvQBfPWKiGASVmNeLOkDGPnl /yjA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@thunk.org header.s=ef5046eb header.b=DIwkJhP3; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b75-v6si20765143pfd.41.2018.06.09.18.51.45; Sat, 09 Jun 2018 18:52:00 -0700 (PDT) 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=fail header.i=@thunk.org header.s=ef5046eb header.b=DIwkJhP3; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753583AbeFJBvX (ORCPT + 99 others); Sat, 9 Jun 2018 21:51:23 -0400 Received: from imap.thunk.org ([74.207.234.97]:53406 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753555AbeFJBvW (ORCPT ); Sat, 9 Jun 2018 21:51:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org; s=ef5046eb; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=wdxLkN0gVRdrEWsrzryhWI3REiFOulFMro7XdrCMGew=; b=DIwkJhP3NEqb7figeUOytV2Z52 JLVBWc0U+Aw2FCyUm8ifP3A4T7mCHyyLaNSWqJ0ZOg0TPTzDjTIsbRIOyNshk6uJg9Gca9Ys94LVs dWvYbSFVWlP7mwPxAJsjTGK516Qjq0G+9g2gzjDyw63vFVWg8ZWjGHjfYSQeygWVCW0U=; Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.89) (envelope-from ) id 1fRpVc-0004SH-I3; Sun, 10 Jun 2018 01:51:08 +0000 Received: by callcc.thunk.org (Postfix, from userid 15806) id C3C787A4474; Sat, 9 Jun 2018 21:51:07 -0400 (EDT) Date: Sat, 9 Jun 2018 21:51:07 -0400 From: "Theodore Y. Ts'o" To: Linus Torvalds Cc: Tetsuo Handa , Dmitry Vyukov , Greg Kroah-Hartman , "Eric W. Biederman" , Guenter Roeck , Linux Kernel Mailing List , Andrew Morton , syzkaller , Stephen Rothwell , David Miller , Wu Fengguang Subject: Re: what trees/branches to test on syzbot Message-ID: <20180610015107.GC5020@thunk.org> Mail-Followup-To: "Theodore Y. Ts'o" , Linus Torvalds , Tetsuo Handa , Dmitry Vyukov , Greg Kroah-Hartman , "Eric W. Biederman" , Guenter Roeck , Linux Kernel Mailing List , Andrew Morton , syzkaller , Stephen Rothwell , David Miller , Wu Fengguang References: <873735n3dy.fsf@xmission.com> <20180116173440.GA15893@kroah.com> <81a0eb59-c204-9e36-13b7-88c2ea99ceab@I-love.SAKURA.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jun 09, 2018 at 03:17:21PM -0700, Linus Torvalds wrote: > I think it would be lovely to get linux-next back eventually, but it > sounds like it's just too noisy right now, and yes, we should have a > baseline for the standard tree first. > > But once there's a "this is known for the baseline", I think adding > linux-next back in and then maybe even have linux-next simply just > kick out trees that cause problems would be a good idea. > > Right now linux-next only kicks things out based on build issues (or > extreme merge issues), afaik. But it *would* be good to also have > things like syzbot do quality control on linux-next. Syzbot is always getting improved to find new classes of problems. So the only way to get a baseline would be to use an older version of syzbot for linux-next, and to have it suppress sending e-mails about failures that are duplicates that were already found via the mainline tree. Then periodically, once version N has run for M weeks, and has spewed some large number of new failures to LKML, then you could promote version N to be run against linux-next, and so hopefully the only thing it would report against linux-next are regressions, and not duplicates of new bugs also being found via the latest and greatest version of syzbot being run against the mainline kernel. - Ted