From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, T_DKIMWL_WL_MED,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DFAEDC43142 for ; Tue, 26 Jun 2018 14:38:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8F1BB26970 for ; Tue, 26 Jun 2018 14:38:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="o6o5IwUS" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8F1BB26970 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965385AbeFZOiz (ORCPT ); Tue, 26 Jun 2018 10:38:55 -0400 Received: from mail-pg0-f65.google.com ([74.125.83.65]:40260 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964772AbeFZOiv (ORCPT ); Tue, 26 Jun 2018 10:38:51 -0400 Received: by mail-pg0-f65.google.com with SMTP id w8-v6so7714658pgp.7 for ; Tue, 26 Jun 2018 07:38:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=SxQroKpBaBKrzbnif2s7oWfECxJ1tmTwJ1hv8zSqWco=; b=o6o5IwUSdTShTdXP0oyId2RQtfYnfEcjwYXhYslYWR7DTAo+nYBX9k/TrQIGsFKCE/ y+xhIcQtReaiIZ/73Okp+QYAR6Dgzl2QC0WmA+8GG58GsF7k3hmDEPhbGV3ctr3Obrlm aYOFy28/gsk0IlTvUrNNZmAitfUZmNpX3uGdQbfQZ9J6pbRDc4pICy+xeeWkYwdwySCU 2c38QHjYHV+lWq7XEPt9mcewlIuNCAKUGfAOuxaJ/VqzvTI4JfdRJA4TH+dYuYYNu/am JMKfVBmjgcysvHIKz42S0+apXPhANfSdoikqKZBskoMw05oeKD7C2zfDirI0cO0Qs2xB a22A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=SxQroKpBaBKrzbnif2s7oWfECxJ1tmTwJ1hv8zSqWco=; b=IgOQPKsa5oGeUqdFTy2coKAHtUD0E6cZ9+dO5BDNtioE5JPPB8ww0y5LNLFBn2W0Be sYmKFOLJBs5ln1ayMsBj9OJVN8RLn7oxZdT/MBURjMlxAg5ioMCPEjOplf8LrqcKR2am UIpPyaR3e3tcYMfR5L7xxlY4ZQwVS/SogX+hN1vttSSx+9Oxn7U3NRcs+7NxhFpuT2z9 6SfJ2CbQuJaiYHcJUy6DC8NtvKVNpiXivY9XlER+yO8WzcYVOgP33XhIi7GhoakxX9uh XXVVG5Uh44NSPpcV7A6VeaxnaJrydvJy2OwShH29VvRLOSDXKBoHDfX8McZeGzmsAJEW HpGw== X-Gm-Message-State: APt69E19ZJtxgz15nshtcTyuTq+gav8kZoYDExBFPRfxTNH1ZlM42Ifz Q1qSgf1k4Z8M0YwYd13w/qlcYgpgZ9UdjV7e0O/ofg== X-Google-Smtp-Source: ADUXVKJoD2fxO9gLnk1SifZmYXLTkRqMd3R1Z0mdhBPoDF8OpuKC4VaFTFLg9NaaZyew/5kcd/w0caZmGEk9n41vpT8= X-Received: by 2002:a65:58c8:: with SMTP id e8-v6mr1644784pgu.96.1530023930355; Tue, 26 Jun 2018 07:38:50 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:de2:0:0:0:0 with HTTP; Tue, 26 Jun 2018 07:38:29 -0700 (PDT) In-Reply-To: <20180626141602.GA17788@thunk.org> References: <873735n3dy.fsf@xmission.com> <20180116173440.GA15893@kroah.com> <81a0eb59-c204-9e36-13b7-88c2ea99ceab@I-love.SAKURA.ne.jp> <20180626141602.GA17788@thunk.org> From: Dmitry Vyukov Date: Tue, 26 Jun 2018 16:38:29 +0200 Message-ID: Subject: Re: what trees/branches to test on syzbot To: "Theodore Y. Ts'o" , Tetsuo Handa , Linus Torvalds , Dmitry Vyukov , Greg Kroah-Hartman , "Eric W. Biederman" , Guenter Roeck , Linux Kernel Mailing List , Andrew Morton , syzkaller , Stephen Rothwell , David Miller , Wu Fengguang Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 26, 2018 at 4:16 PM, Theodore Y. Ts'o wrote: > On Tue, Jun 26, 2018 at 07:54:53PM +0900, Tetsuo Handa wrote: >> I hope we can accept NOW either "reviving linux-next.git" or "allowing debug printk() >> patches for linux.git". For example, "INFO: task hung in __sb_start_write" got 900 >> crashes in 81 days but still unable to find a reproducer. Dmitry tried to reproduce >> locally with debug printk() patches but not yet successful. I think that testing with >> http://lkml.kernel.org/r/f91e1c82-9693-cca3-4ab7-ecd9d9881fb4@i-love.sakura.ne.jp >> on linux.git or linux-next.git is the only realistic way for debugging this bug. >> More we postpone revival of the linux-next, more syzbot reports we will get... > > Here's a proposal for adding linux-next back: > > *) Subsystems or maintainers need to have a way to opt out of getting > spammed with Syzkaller reports that have no reproducer. More often > than not, they are not actionable, and just annoy the maintainers, > with the net result that they tune out all Syzkaller reports as > noise. False. You can count yourself. 2/3 are actionable and fixed. This also makes the following point ungrounded. > *) Email reports for failures on linux-next that correspond to known > failures on mainline should be suppressed. Another way of doing > this would be to only report a problem found by a specific > reproducer to the mailing list unless the recipient has agreed to > be spammed by Syskaller noise. > > And please please please, Syzkaller needs to figure out how to do > bisection runs once you have a reproducer. > > - Ted