Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E7BC9C6FA99 for ; Tue, 7 Mar 2023 21:45:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231484AbjCGVph (ORCPT ); Tue, 7 Mar 2023 16:45:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54548 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230362AbjCGVpf (ORCPT ); Tue, 7 Mar 2023 16:45:35 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E4C6FA18B7; Tue, 7 Mar 2023 13:45:28 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 9B2D9B81A1D; Tue, 7 Mar 2023 21:45:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 35DCEC4339B; Tue, 7 Mar 2023 21:45:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1678225526; bh=HH8mJ1XwzzJVj0SV4GpOAl0LULKJW0qe4QV7EO1mXAg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=qYOPwrerPTTlhpHpsXrpuQ80dZPP680H+k/302Jkk0wa3w1dlwnEvfDjKnxwK/8xC PUxteEzrXOI1vGaaLn1xx2LHEGexfd/i1JCh1LttzLAs7uoTuzfamUAE6ckTg17uxf cRXjz0h7+aYLBtf5OB0z4P0UnH/d68v9TnbLSIrhYi2vEoTZG48t+GEVG4GX7YPDyL WoyzDUIyGFrD5eGv9fibkdC2v/yd7X4Wi3DmBURR1dtiwlRgcNf+BzMWxiszepOIkK CF0EoXOrWNMkwSpplgA/tMDyImZumOEpRPCQrDIWmNVF2w3x9SwJejLWsEER2RpoYu CZNFnMeRfvvkQ== Date: Tue, 7 Mar 2023 21:45:24 +0000 From: Eric Biggers To: Pavel Machek Cc: Sasha Levin , linux-kernel@vger.kernel.org, stable@vger.kernel.org, viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org Subject: Re: AUTOSEL process Message-ID: References: <20230226034256.771769-1-sashal@kernel.org> <20230226034256.771769-12-sashal@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 07, 2023 at 10:18:35PM +0100, Pavel Machek wrote: > Hi! > > > > So to summarize, that buggy commit was backported even though: > > > > > > * There were no indications that it was a bug fix (and thus potentially > > > suitable for stable) in the first place. > > > * On the AUTOSEL thread, someone told you the commit is broken. > > > * There was already a thread that reported a regression caused by the commit. > > > Easily findable via lore search. > > > * There was also already a pending patch that Fixes the commit. Again easily > > > findable via lore search. > > > > > > So it seems a *lot* of things went wrong, no? Why? If so many things can go > > > wrong, it's not just a "mistake" but rather the process is the problem... > > > > BTW, another cause of this is that the commit (66f99628eb24) was AUTOSEL'd after > > only being in mainline for 4 days, and *released* in all LTS kernels after only > > being in mainline for 12 days. Surely that's a timeline befitting a critical > > security vulnerability, not some random neural-network-selected commit that > > wasn't even fixing anything? > > I see this problem, too, "-stable" is more experimental than Linus's > releases. > > I believe that -stable would be more useful without AUTOSEL process. > There has to be a way to ensure that security fixes that weren't properly tagged make it to stable anyway. So, AUTOSEL is necessary, at least in some form. I think that debating *whether it should exist* is a distraction from what's actually important, which is that the current AUTOSEL process has some specific problems, and these specific problems need to be fixed... - Eric