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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 321C3C433E0 for ; Tue, 23 Mar 2021 18:09:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id ECC756192B for ; Tue, 23 Mar 2021 18:09:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231378AbhCWSIa (ORCPT ); Tue, 23 Mar 2021 14:08:30 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:55250 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S231352AbhCWSIF (ORCPT ); Tue, 23 Mar 2021 14:08:05 -0400 Received: from cwcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 12NI7RRV010579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 23 Mar 2021 14:07:28 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 763FF15C39CC; Tue, 23 Mar 2021 14:07:27 -0400 (EDT) Date: Tue, 23 Mar 2021 14:07:27 -0400 From: "Theodore Ts'o" To: Steven Rostedt Cc: Thorsten Leemhuis , Linus Torvalds , Greg KH , Linux Kernel Mailing List , ksummit , workflows@vger.kernel.org, Konstantin Ryabitsev Subject: Re: RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions Message-ID: References: <613fe50d-fc9c-6282-f1f3-34653acb2ee9@leemhuis.info> <62b60247-7838-a624-706e-b1a54785b2a5@leemhuis.info> <20210323122025.77888b49@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210323122025.77888b49@gandalf.local.home> Precedence: bulk List-ID: X-Mailing-List: workflows@vger.kernel.org On Tue, Mar 23, 2021 at 12:20:25PM -0400, Steven Rostedt wrote: > On Mon, 22 Mar 2021 20:25:15 +0100 > Thorsten Leemhuis wrote: > > > I agree to the last point and yeah, maybe regressions are the more > > important problem we should work on – at least from the perspective of > > kernel development. But from the users perspective (and > > reporting-issues.rst is written for that perspective) it feel a bit > > unsatisfying to not have a solution to query for existing report, > > regressions or not. Hmmmm... > > I think the bulk of user issues are going to be regressions. Although you > may be in a better position to know for sure, but at least for me, wearing > my "user" hat, the thing that gets me the most is upgrading to a new kernel > and suddenly something that use to work no longer does. And that is the > definition of a regression. My test boxes still run old distros (one is > running fedora 13). These are the boxes that catch the most issues, and if > they do, they are pretty much guaranteed to be a regression. I think it depends on the user and the subsystem. You're a sophisticated user, but I've fielded a goodly number of ext4 "bug reports" which were coming from a Ubuntu 16.04 kernel, or a user who is seeing a block device issue (either a driver bug or a hardware failure), or in some cases both. A lot of these "bug reports" would be headed off at the pass if we advertised: https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html much more heavily; assuming we can get the users to actually read it, first. - Ted