Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp481343imm; Thu, 5 Jul 2018 03:51:08 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcXlaPbZPhy9xJMlLsdpiyQAcCdl8bIImxcmemGDKYIvO25SvKgAypVlDo6I9DIlMczSB44 X-Received: by 2002:a17:902:14b:: with SMTP id 69-v6mr5695813plb.184.1530787868002; Thu, 05 Jul 2018 03:51:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530787867; cv=none; d=google.com; s=arc-20160816; b=i+o+Xtp5n/vr9M820seZjwGnDlZwaW/uPl8+ohoL1MAJTYMPbZHQrHuc3PUXnpRktQ JFNJcpypYTpOkiNXi8c5eoLiM8dVY8BWNah8OiJGuxXuV7poembG4nKMtVfqxZloUC24 /YRoc9sA3bgEP4imDH1sc8oqbmlOoEz9SP6y8MdKKC22fTAvIfW1JYVxf9ofIZPKhQUs X4DIN3bYWfQJAhPpsgO7tqPOkuiAMhehmG2YtKQq1B2K5Fz2qjob7t9PC6ciev4NKSvv w6bESNdWsnRl9zfoYfO5W/zc9yGjHNgIzz55yl4Z3eKsY/SUd9+BW0GJwsdcDLUnQdX8 H5NQ== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=U8cF7LJbChAI/yqzILfkH+QrSO7qFcAmKtdPa48D8qA=; b=XIzeQoO9MRXE6u7IA7zH5yOH2GPtsE1yZ1A9+HWqgotqdyVm62lPq9TWHgbQie7i0T R4tRr//Mzq1yTr1+2fX0V2PgKp66GhJrF1k2RGFlKeHKGYpAW02ep8aVOBFrhqlFBjhk j1iGeWzN8Lyu1DYdHHZkG4+coy06Gyw41zhlkESrbLnKYjAyjpk2tjaphmwtw7tTtKrI 8PeYSvdYD4odRIaTttztfavJhDeIKUCU3VnRa5oRtsWOzC9IamsVZ8hma/dD9HXyl3b1 2WEWk8qqUjKXpGsHFitL1gFhQlSqak/boRB49OEBmmtVKfEoRZSV37URgyASAMQeA2Gf /yjA== 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 t66-v6si5177692pgt.538.2018.07.05.03.50.53; Thu, 05 Jul 2018 03:51:07 -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 S1753797AbeGEKt6 (ORCPT + 99 others); Thu, 5 Jul 2018 06:49:58 -0400 Received: from www262.sakura.ne.jp ([202.181.97.72]:59031 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753499AbeGEKt5 (ORCPT ); Thu, 5 Jul 2018 06:49:57 -0400 Received: from fsav302.sakura.ne.jp (fsav302.sakura.ne.jp [153.120.85.133]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id w65AnGRl094367; Thu, 5 Jul 2018 19:49:16 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav302.sakura.ne.jp (F-Secure/fsigk_smtp/530/fsav302.sakura.ne.jp); Thu, 05 Jul 2018 19:49:16 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/530/fsav302.sakura.ne.jp) Received: from [192.168.1.8] (softbank126074194044.bbtec.net [126.74.194.44]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id w65An9QU094310 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Jul 2018 19:49:16 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Subject: Re: what trees/branches to test on syzbot To: Dmitry Vyukov Cc: Guenter Roeck , "Theodore Ts'o" , Linus Torvalds , Greg Kroah-Hartman , "Eric W. Biederman" , linux-kernel , Andrew Morton , syzkaller , Stephen Rothwell , David Miller , kbuild test robot References: <873735n3dy.fsf@xmission.com> <20180116173440.GA15893@kroah.com> <81a0eb59-c204-9e36-13b7-88c2ea99ceab@I-love.SAKURA.ne.jp> <20180626141602.GA17788@thunk.org> <876e38d9-95e5-0a93-9c26-7287151b8b53@i-love.sakura.ne.jp> From: Tetsuo Handa Message-ID: <8c9027d6-ead2-1cca-4410-c8dbbe4bf2ea@I-love.SAKURA.ne.jp> Date: Thu, 5 Jul 2018 19:49:10 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <876e38d9-95e5-0a93-9c26-7287151b8b53@i-love.sakura.ne.jp> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018/06/27 5:37, Tetsuo Handa wrote: > I think that syzbot can stop deciding email recipients and leave it to those who > diagnose bugs, for the ratio of sending to wrong subsystem maintainers is not low. > For example, syzbot assumed that "INFO: task hung in __get_super" is a fs layer bug. > But I think that the problem is in more lower layers (block or mm or locking layer). > The root cause could even be just overstressed due to instructions enabled by > CONFIG_KCOV_ENABLE_COMPARISONS=y. > Thinking from today's bpf related reports, I think that subversion/quilt-based custom patches will be useful as well. Since quilt can apply changes in a patch atomically (using "quilt push" command), we can maintain one custom patch for one git tree. Then, the kernel source syzbot will test is either "no custom patch applied" or "only one custom patch applied". That is, if "quilt push" fails, syzbot will continue testing without custom patch. Since subversion manages revision number using an integer, adding a column for indicating "which custom patch was applied for this report" to the table will not occupy much space. We will figure out that custom patch needs to be updated via syzbot reports with that column being empty. The custom patch can contain whatever changes which might be useful for debugging. For example, debug printk() for "INFO: task hung in __sb_start_write" case. For another example, context identifier for printk(). Updating custom patches in subversion repository is done manually. But the cost is negligible.