From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f198.google.com (mail-wr0-f198.google.com [209.85.128.198]) by kanga.kvack.org (Postfix) with ESMTP id 303036B0009 for ; Tue, 17 Apr 2018 06:39:45 -0400 (EDT) Received: by mail-wr0-f198.google.com with SMTP id e15so15989586wrj.14 for ; Tue, 17 Apr 2018 03:39:45 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com. [66.111.4.27]) by mx.google.com with ESMTPS id 8si144978edw.155.2018.04.17.03.39.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Apr 2018 03:39:43 -0700 (PDT) Date: Tue, 17 Apr 2018 12:39:36 +0200 From: Greg KH Subject: Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes Message-ID: <20180417103936.GC8445@kroah.com> References: <20180416155031.GX2341@sasha-vm> <20180416160608.GA7071@amd> <20180416161412.GZ2341@sasha-vm> <20180416170501.GB11034@amd> <20180416171607.GJ2341@sasha-vm> <20180416203629.GO2341@sasha-vm> <20180416211845.GP2341@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Jiri Kosina Cc: Sasha Levin , Pavel Machek , Linus Torvalds , Steven Rostedt , Petr Mladek , "stable@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "akpm@linux-foundation.org" , "linux-mm@kvack.org" , Cong Wang , Dave Hansen , Johannes Weiner , Mel Gorman , Michal Hocko , Vlastimil Babka , Peter Zijlstra , Jan Kara , Mathieu Desnoyers , Tetsuo Handa , Byungchul Park , Tejun Heo On Mon, Apr 16, 2018 at 11:28:44PM +0200, Jiri Kosina wrote: > On Mon, 16 Apr 2018, Sasha Levin wrote: > > > I agree that as an enterprise distro taking everything from -stable > > isn't the best idea. Ideally you'd want to be close to the first > > extreme you've mentioned and only take commits if customers are asking > > you to do so. > > > > I think that the rule we're trying to agree upon is the "It must fix > > a real bug that bothers people". > > > > I think that we can agree that it's impossible to expect every single > > Linux user to go on LKML and complain about a bug he encountered, so the > > rule quickly becomes "It must fix a real bug that can bother people". > > So is there a reason why stable couldn't become some hybrid-form union of > > - really critical issues (data corruption, boot issues, severe security > issues) taken from bleeding edge upstream > - [reviewed] cherry-picks of functional fixes from major distro kernels > (based on that very -stable release), as that's apparently what people > are hitting in the real world with that particular kernel It already is that :) The problem Sasha is trying to solve here is that for many subsystems, maintainers do not mark patches for stable at all. So real bugfixes that do hit people are not getting to those kernels, which force the distros to do extra work to triage a bug, dig through upstream kernels, find and apply the patch. By identifying the patches that should have been marked for stable, based on the ways that the changelog text is written and the logic in the patch itself, we circumvent that extra annoyance of users hitting problems and complaining, or ignoring them and hoping they go away if they reboot. I've been doing this "by hand" for many years now, with no complaints so far. Sasha has taken it to the next level as I don't scale and has started to automate it using some really nice tools. That's all, this isn't crazy new features being backported, it's just patches that are obviously fixes being added to the stable tree. Yes, sometimes those fixes need additional fixes, and that's fine, normal stable-marked patches need that all the time. I don't see anyone complaining about that, right? So nothing "new" is happening here, EXCEPT we are actually starting to get a better kernel-wide coverage for stable fixes, which we have not had in the past. That's a good thing! The number of patches applied to stable is still a very very very tiny % compared to mainline, so nothing new is happening here. Oh, and if you do want to complain about huge new features being backported, look at the mess that Spectre and Meltdown has caused in the stable trees. I don't see anyone complaining about those massive changes :) thanks, greg k-h