Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp102401ybb; Thu, 9 Apr 2020 18:14:55 -0700 (PDT) X-Google-Smtp-Source: APiQypI9BLc18/E+klY9XM1yA5VL+pRS0JrWyg0RoyELx46jFI8w9F+CY0+/hRoZ1/QkkPk+awIL X-Received: by 2002:ac8:5048:: with SMTP id h8mr2282804qtm.189.1586481295607; Thu, 09 Apr 2020 18:14:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586481295; cv=none; d=google.com; s=arc-20160816; b=XhZEnpBeyrqvMQZCXx8Vt+MNN4jFPgV3d9CMRKy7dwkMEBK3EveSISMDfOH2a009em QxiWOdT8NapsfEfEla8+CL0lot7nKoJXiEDVuc9dHJFgRTmQkHOsoUspNrXYgX/09w/B BAKOYDMp3zIGxq9FVIUx1xlDfPh1PO81jBA4wRZCR0wkJsci8/5HZTnIrLi7TBsNwCtR TIebdHHp4Mic2lQJvCNZIDN90a85TU7JzBI/Q8RDb8jiL6rNx5iVrqnbUe8e0OEpULE/ +2utWxkCs5nhRntUwW58gOgth+G95svjEKt2Caml8vJ32EbGx5Fh806MW6i/UdHR0spm 5xqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=6tmUVQyAoqG+ygThhSpu+bhVLBEnsW0XZFxrjybDnxk=; b=L3pnjL89JpMVUdi07swzPJ38ZmRzAdXZi7D4P3yxZSW1fRGjbTGuJXAT/nAw7DoB+p 6iYP/4qt3xW87XI6wB7+LxvCJ0YTEQbVl5UinTY9RSVVtEE05ByqsqgQSzev1Ow8u/kN hyg6kGkVem1AE/oWSr1ComBpQ+fkx8TKOhM8rvmeEkq3f6dt3/FPRsMBPbQQO13d2LTa Fi6204CB+wpWTn6kYahYSozx+vCHECmj+2mnh3ILCN3ViiQwMKoz3NklRVyzsG3PDjfL /obr5ZNjaWelIWBYkuSV2OeD9PITXObRiE7JY/DJpVsvi+0WeyuwKcZv/3qPOBcwii2B iXeA== 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 s12si318484qti.43.2020.04.09.18.14.39; Thu, 09 Apr 2020 18:14:55 -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 S1726594AbgDJBMG (ORCPT + 99 others); Thu, 9 Apr 2020 21:12:06 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:39282 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725987AbgDJBMG (ORCPT ); Thu, 9 Apr 2020 21:12:06 -0400 Received: from callcc.thunk.org (pool-72-93-95-157.bstnma.fios.verizon.net [72.93.95.157]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 03A1BYn0032116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 9 Apr 2020 21:11:35 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id 4500142013D; Thu, 9 Apr 2020 21:11:34 -0400 (EDT) Date: Thu, 9 Apr 2020 21:11:34 -0400 From: "Theodore Y. Ts'o" To: Linus Torvalds Cc: Eric Biggers , Matthew Wilcox , Andrew Morton , Dmitry Vyukov , Peter Xu , LKML , Linux-MM , syzkaller-bugs , Stephen Rothwell Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports Message-ID: <20200410011134.GG45598@mit.edu> References: <20200409114940.GT21484@bombadil.infradead.org> <20200409111604.c778ff091c00fab5db095e48@linux-foundation.org> <20200409121250.d6bba6965b86c8dfcf325fbc@linux-foundation.org> <20200409195633.GZ21484@bombadil.infradead.org> <20200409202751.GA7976@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 09, 2020 at 01:34:18PM -0700, Linus Torvalds wrote: > > FWIW, the issue of "syzbot report sent and ignored for months/years" is actually > > a much broader one which applies to all bugs, not just build / test breakages. > > I don't know what to do about that, but it may be that people just > don't judge the bugs interesting or assume that they are old. Syzkaller bugs which requuire (a) root privileges to trigger, or (b) require a deliberately corrupted file system are things which I don't consider super interesting. (For the latter, I'll usually wait for some other file system fuzzer to find it, such as Hydra, because Syzkaller makes it painful extract out the file system image, where as other file system fuzzers are *much* more file system developer friendly.) This shouldn't be a surprise to Dmitry, because I've given these feedbacks to him before. It would be nice if there was some way we could triage Syzkaller bugs into different buckets (requires root, lower to P2; requires a corrupted file system image, lower to P2). Unfortunately, that would require Syzkaller to have some kind of login system and way to track state, and Dmitry doesn't want to replicate the functionality of a bug tracker. > That's what made bugzilla so useless - being flooded with stale bugs > that might not be worth worrying about, and no way to really tell. At least with Bugzilla, it becomes possible to attach priorities and flags to them, instead of trying to assume that developers should treat all Syzkaller bugs as the same priority. Because when you do insist that all bugs be treated as high priority, many people will just treat them *all* as a P2 bug, especially when there are so many. - Ted