Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp3116967rwl; Fri, 6 Jan 2023 16:10:25 -0800 (PST) X-Google-Smtp-Source: AMrXdXu3cgKT0MCwac7wdOWBrBO67nR3RbEtMJaZK8BIQLKEllZTuok8lgCzmCBfpxcvLX4FX3IF X-Received: by 2002:a17:902:8481:b0:193:e20:a5a9 with SMTP id c1-20020a170902848100b001930e20a5a9mr3836928plo.15.1673050225758; Fri, 06 Jan 2023 16:10:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673050225; cv=none; d=google.com; s=arc-20160816; b=0w135jv6ocREiWbGxFlELoCKRvtB3FLxpvrX6D+RprP01Pxl0Z/rVAQCwGMNT1EGKM wTwUDenxwjBUWGoo3B6NpXEN4bNvC0yA7qV+zBdt1SB+6S89I5c6my4wBi3MP+AvpKUK 5oJxKlyrA1qGd7GF+Gqx4vPi7KtNGiWuLZoaSA9kxOWjuG2URCajuJ1osGoq7k0knn4K W/MTGcs1619wGfuFD7sushGEI7QOtu9nTJFX3cf2z0e42vlUti7XM3UtRR2+VOJ+bvDy MD5lc0HrFF/wACIp2GGJLtXSwvE5F6uuhweenqrwTXZhdZL4Ds+RX4Ifu3RYf9WJM6Nn ra4g== 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-disposition:mime-version :references:message-id:subject:cc:to:from:date:feedback-id :dkim-signature:dkim-signature; bh=7G4/beSUaFqqw1nEdaUkVcwlLhwLsSrWTndJbny1Uek=; b=ucpsmtI0AXekQKTBTwJr29ZdifTERgqQ/w10xbtCCGHwgLMEiR632fYaf7nwgWp7zR 8TTyAgaoyCVv3m18Dh9i2sX08UOG/3B1fP2X/UFBRnPKwGrmGebooHmdVQV0cO9MOaMv KW5pL25/jtnEKOaGW3gCGMtfNCoS+kq2am5qyayIu6YuW4BeeLTPB/639ocN7g1v6h6l +DwUDUPeIXlIalR98bwXaVmma9gYlVoN6O0k6h5zdUpF9eLcqoVjUCMDc2OHvwSf5s0r V8Obb30oyxnDJCj8etJ9cd15EjFVc/QZJjX1vUx33wMkUo8SkJGUd9gZs0RfCujxvVJ0 spsg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@tyhicks.com header.s=fm2 header.b=hGJkAkQ5; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=mBm7DiKm; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z12-20020a170902834c00b0017f7fffb591si2134477pln.374.2023.01.06.16.10.18; Fri, 06 Jan 2023 16:10:25 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@tyhicks.com header.s=fm2 header.b=hGJkAkQ5; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=mBm7DiKm; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235512AbjAFXxV (ORCPT + 55 others); Fri, 6 Jan 2023 18:53:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54978 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229780AbjAFXxT (ORCPT ); Fri, 6 Jan 2023 18:53:19 -0500 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AE46C72D22; Fri, 6 Jan 2023 15:53:18 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B09D85C0071; Fri, 6 Jan 2023 18:53:14 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 06 Jan 2023 18:53:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tyhicks.com; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm2; t=1673049194; x=1673135594; bh=7G4/beSUaF qqw1nEdaUkVcwlLhwLsSrWTndJbny1Uek=; b=hGJkAkQ5KCG0r0+DxIojSkT5BC IBN6kbZKQq7pLRwfGGaNKDfW+LGae89wtH1h2F8OPrqSZ7MWp1xANmLhMrq/7CqJ UNqfC8L2Dlzzoxk/fnYY8jVpJ+N+iQEIPkNYfO9/Kpth32Hfx3FfSlbZABAW3bL0 e8oXoaSlZ0m8HF7C9agSc3jtdXjob4z63GM6FftCC2GZmPeLWefHKApzyc8XXbe1 tmDr9pdDjkNQlu9xMya+nqSPue+SBmEGqmpCbDAbEbeRMGRUDezeYx/rB3dGCe7d CGYSC5I2zJfTUJaR4eYiizl3dvCBHKDNb8llrGznk30FAS0UfV0ckudA/XbA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1673049194; x=1673135594; bh=7G4/beSUaFqqw1nEdaUkVcwlLhwL sSrWTndJbny1Uek=; b=mBm7DiKmDzFj3ZH0irV4Ph9MbVV6esIQVuP890YNs3Ms 2J3Q9JMWOXIu2joi/yhJVzqCuH7q+kP2TOYHGSGRN0xJYhdAYcWmRnHqRbr0h3ii sIHPmp2KZoQVBcUUgUoI2ppwseRIKl6NOC1odHgJPaUOhE+ZZKBy2VhVff63nT8w ydtyxhgUHKR71tOO6medUr3Neq/JyZRIWsCX4TVnto4uuXA8xfnyjTVKXr2PVyou zTFbQdhDXelcxMqZbNLEkDWFWfwEo0deTwQi/Qf26grzK9x638wwn+hN6WOmhLpN 4uyqXwZ0wWEYQ8pMnbzBfn548+EwqttdaRTrhflX5w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrkedugdduhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefvhihlvghr ucfjihgtkhhsuceotghouggvsehthihhihgtkhhsrdgtohhmqeenucggtffrrghtthgvrh hnpeetveeffeehgefgieffudeulefgffegudehjeejueffvefhkedvhfelvdevffelhfen ucffohhmrghinhepkhgvrhhnvghlrdhorhhgpdhlvggvmhhhuhhishdrihhnfhhonecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheptghouggvseht hihhihgtkhhsrdgtohhm X-ME-Proxy: Feedback-ID: i78e14604:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 6 Jan 2023 18:53:12 -0500 (EST) Date: Fri, 6 Jan 2023 17:53:10 -0600 From: Tyler Hicks To: Greg Kroah-Hartman Cc: Pavel Machek , stable@vger.kernel.org, patches@lists.linux.dev, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org, lkft-triage@lists.linaro.org, jonathanh@nvidia.com, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de Subject: Re: [PATCH 6.1 000/207] 6.1.4-rc1 review Message-ID: References: <20230104160511.905925875@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023-01-06 07:58:45, Greg Kroah-Hartman wrote: > On Thu, Jan 05, 2023 at 08:34:08PM +0100, Pavel Machek wrote: > > Hi! > > > > > This is the start of the stable review cycle for the 6.1.4 release. > > > There are 207 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > Thank you. > > > > Is it known at this point if 6.1 will became next longterm release? It > > is not listed as such on https://www.kernel.org/category/releases.html > > . We might want to do some extra testing if it is. > > A kernel can not become "long term" until it would have normally dropped > off of support. Right now there are known-regressions in 6.1 still that > are not resolved. Hey Greg - A couple questions... 1. Does that mean that you always wait until N+1 is released by Linus before declaring N to be an upstream LTS kernel? Looking back to last year, v5.16 was released on 2022-01-10 and you declared v5.15 as the LTS on 2022-01-16: https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=c335525958a3424ec0200dc9093d2bbf95032f83 That one data point lines up but I want to confirm that's the normal procedure because I hadn't noticed that pattern until now and I don't see it mentioned on the kernel.org Releases page. 2. Do you (or anyone else) happen to have a list of the known regressions? I see one specific to linux-6.1.y in the regzbot list: https://linux-regtracking.leemhuis.info/regzbot/stable/ Another reported here (with a potential fix identified): https://lore.kernel.org/netdev/CAK8fFZ7cYRkGjUJD2D86G6Jh9YRmP_L+7Ke6CLFSyFmRkoe-Hg@mail.gmail.com/T/#m1b118647969eb0d64de016858506fc2345a0b834 A more complete list may help all of us currently evaluating v6.1. > And "extra" testing is always good no matter what kernel branch it is > happening for, why not always do it? That's a very good point. I have to admit that we are a bit too LTS-focused today when it comes to our testing. We have a goal to improve in that area. We have been working under the assumption that v6.1 is going to be the next LTS but, as you point out, we should be iteratively testing each release just the same. We are currently doing some additional/extra testing of v6.1 with our Microsoft Linux kernel and will let you know the results as they come in. Tyler > > thanks, > > greg k-h