Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3954168imm; Mon, 18 Jun 2018 06:56:21 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKmtipnA7BHpmIT+3bexT79Ie9A7teIaR4eLvgdXqVXTNkXKJm9HB4SeVB1xWN6mQsJLKv2 X-Received: by 2002:a17:902:9a4c:: with SMTP id x12-v6mr14224895plv.213.1529330181273; Mon, 18 Jun 2018 06:56:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529330181; cv=none; d=google.com; s=arc-20160816; b=tpRqxxI3IKGtpkhjC5PJ/86keZmdwbAwUjpV8V5+l0P6Ckdg5SE8ZgzVdmZ2OwCF1A GvB5CfKmL+zNdddycD/OyjgJELV7IqY5N/cbQR4LZURZJq4bagtKDDhe+6KXfh9zoCtP ht/N5/uIJbYqLej1xTyJpOpu9PPQYjSkjkHw5ytbliHCYYGr/uVikspnCyaFDSuhCxba UH/FjZDHIwyF5ppwSLbHHXx9c//aZa6Q+6W1rgvXIEdA6YAID6D7Uy7iLdIlOtlMNp28 sqlWVpD2fljZ2KE2CmK0WTptWzOfuq3Qn4E5VL0C3BE9UY8585CXsJwRpQTvZtQjf1LN K4Dg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=m8FIMtP664sLiEF3RIwbWvrDZugbg4mT6MhJyqPk5tU=; b=O2iGOA6m1+hVCmltmhZbve7etfI0ttyPZq/2bqjNsRvWoYK8ovmh1NDo9vt5+I/Mws UGnIRqr/cg/z1jt4HCmuIcidwDQU6UK2Dg0V+UdlHOydfWUbx0hOJ9XpV8MBFPI/hNYv D4ZdQkWRF/FYnTnWT6887lABqOt61bT8qcfjtUdr1UPRRz5134KuFB09FQkIhM3PX30h KwDida3dAPGZ6vlGEotMMQbpEPzt3NXLO3LHzXxhnUNG3KUu4m3h9cloTBGg+pb2tsAE ccXuHKqe+bYOMVq8sIso7Z9fiXNjygs8iup84CmZUVkeYOiX7js3WZKj3vmKWuGbqYeg LtoA== ARC-Authentication-Results: i=1; mx.google.com; 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 n12-v6si14550246plp.123.2018.06.18.06.56.06; Mon, 18 Jun 2018 06:56:21 -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; 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 S1754659AbeFRNzT (ORCPT + 99 others); Mon, 18 Jun 2018 09:55:19 -0400 Received: from www.llwyncelyn.cymru ([82.70.14.225]:33358 "EHLO fuzix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754601AbeFRNzS (ORCPT ); Mon, 18 Jun 2018 09:55:18 -0400 Received: from alans-desktop (82-70-14-226.dsl.in-addr.zen.co.uk [82.70.14.226]) by fuzix.org (8.15.2/8.15.2) with ESMTP id w5IDsNpk007745; Mon, 18 Jun 2018 14:54:23 +0100 Date: Mon, 18 Jun 2018 14:54:22 +0100 From: Alan Cox To: Dmitry Vyukov Cc: "Theodore Y. Ts'o" , Linus Torvalds , Tetsuo Handa , 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: <20180618145422.11b61298@alans-desktop> In-Reply-To: References: <873735n3dy.fsf@xmission.com> <20180116173440.GA15893@kroah.com> <81a0eb59-c204-9e36-13b7-88c2ea99ceab@I-love.SAKURA.ne.jp> <20180610015107.GC5020@thunk.org> <20180611012250.GD5020@thunk.org> Organization: Intel Corporation X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > But forward bisection (when bug is fixed) unfortunately won't work > because these commits are not connected to HEAD. And forward bisection > is very important, otherwise who will bring order to all these > hundreds of open bugs? > https://syzkaller.appspot.com/ Bisection isn't so important when you are trying to close bugs that got fixed, with a note that it's no longer reproducable. It might mean the reproducer broke but it also stops you drowning and it tells a user that they might as well try the new one and see if still breaks thus collecting the information needed. True it's nice to know what commit may have magically fixed it but it's not essential. Further more once you see a bug is fixed even in -next you can later run the reproducer against an actual release to make sure it's still fixed there, and bisect between previous release and that release to find a mainline commit id if it's a single fix point. Alan