Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4464928pxf; Tue, 23 Mar 2021 11:12:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw7AArN1DJ76epQkzig1VPeqEY4hPbVxyTxYBDBkSOS31CHChHHAzkOFtRPG1sz1gjdR8M2 X-Received: by 2002:a17:907:75d9:: with SMTP id jl25mr6013114ejc.452.1616523132019; Tue, 23 Mar 2021 11:12:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616523132; cv=none; d=google.com; s=arc-20160816; b=fKI97zww0Fb5jGvQFhveiHCOolidDWcahPcLbLnQLQ+wxzrC+caN2s+y1xbqQhGOaW PxQJ2WL4IjtMxytn/PykmzNxJm/P0cX1hujg8HNLPHwicQp1ditEpAVOgmi4xLpVCdeu o9UHIRFi1xo6XHZl33BCm5F+VgyafkQPqcTHqoMYw28Kc9c1Rt+7NRcUVNCo6Y7iHjhN LFN7SwGq4TJuRyUFOOieV/EBs6bnuJT/Uu6CngVdZnLdtN9rxMJBKaUg8R4oetgmT1YZ m0Wton8zsaG9NCwSA/FhqkRXQ8iIxOWw9PhFI/FORiqP8EVQlZH4GPTBuYQqv92+Pm7J Ki3w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=is8TORauGH0gnidgiFMVAAgu8dWwovDFZx6OEbDQ928=; b=u+a6aT0T3hB8UYGGO6C+DsznL/oD1MpV4t0P3SQ+NxVWAyAgV6poJqE0jIfZtSGzCR /bWo1Cvlt84FXXR/sHUk2xZsh7xbjUsPsGvwzoniILiQJaA3UiWoekyP+TCxvyu47a9I mZFD7yWvMGiFw89106SiGxKiUg4egRcJPAW7JuGpEsw4YddVUEmycdBxZNHsf9yGTnkB 2j1P+JnrSqBkdBeEmeOkwQ0g1GwJmJ07cPD4WRUKhUu7dGXTpMVUSSs+0f2fSmn0A4wo brujddTzZSvehjGRw/u63xB/EUQn1/Ws6jc2E45/W4cvbUc20oP54Ii032ue/A0/CfLc hqtw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r9si14029009ejx.201.2021.03.23.11.11.47; Tue, 23 Mar 2021 11:12:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231206AbhCWSIc (ORCPT + 99 others); Tue, 23 Mar 2021 14:08:32 -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: linux-kernel@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