Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751478AbeAPJ7R (ORCPT + 1 other); Tue, 16 Jan 2018 04:59:17 -0500 Received: from mail-pl0-f42.google.com ([209.85.160.42]:37265 "EHLO mail-pl0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751407AbeAPJ7N (ORCPT ); Tue, 16 Jan 2018 04:59:13 -0500 X-Google-Smtp-Source: ACJfBou0fUAif7ypgaEUqRN0AEkure175XzQKfba20M+3P3KZo1f4vUr10a/dxaxjt7d7lxCEbZhl89RteMaXltNOLE= MIME-Version: 1.0 In-Reply-To: References: From: Dmitry Vyukov Date: Tue, 16 Jan 2018 10:58:51 +0100 Message-ID: Subject: Re: what trees/branches to test on syzbot To: Guenter Roeck Cc: LKML , "Theodore Ts'o" , "Eric W. Biederman" , Greg Kroah-Hartman , Andrew Morton , Linus Torvalds , syzkaller , Stephen Rothwell , David Miller , Fengguang Wu Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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?