Received: by 10.192.165.156 with SMTP id m28csp1080063imm; Mon, 16 Apr 2018 13:47:50 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/6zOkkHxZfB9G71AJPRh1EeuJnpooFOPsVRceEt2xcOV9Y7nlmC7/pyypQgGD0VVKW7yki X-Received: by 10.101.90.129 with SMTP id c1mr4876740pgt.20.1523911670844; Mon, 16 Apr 2018 13:47:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523911670; cv=none; d=google.com; s=arc-20160816; b=XWfHtGy8I+yhlkGA7fS/bQ1b+Zuymrf4Ii7SsqKFrFDKZjfc7nq7jy6sqEd/W8zZu8 8YPBeeofchSyuqzHQG+9lUwOVXjIvMbJG4IXshNvrvTLdftM1kzGcj1Z+XcvugoeLwgA L65AZqhQzha6NnFze/nT1DZgr1Aix7oGC83E6KsgCnX4TYSgLb3BzQjbg/IlG8Q0kVXn 7wF32UBfzlALeHCqBGmHG/aWUgPRP17YORGlADR3a356zZJH9kguz6CwJgM4Ygs/dw9P ACq2yU+LFGeD+OMuBDWDlTYT8aaCowxGOMKH4NzpY4u17etsiFtI6g4XV03zlEpKVQoY mh5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=haUKgQ0DbHArKZhJbOuF7blwdlVHnTiGJhDDrUbW9fo=; b=HijcwALP5N6Vp8s4+qey/xR6im5jr1iIogQ5045cJsvlnJ2h6edcXwrCLXEEc8YvT0 NItmSMPCbsk1Ex8vKV1G72tm6t2xemgk0nCub7P5mrXT/KSOHTgzucHA5tZGfdGNCnPz zBEUY3WuDvv4wZEd165HeIYzv6XCBFr43xRCT4BGKrf4SW/AEKupV5xuHP/Hw/K4b2nw g3a8+ShJxHbTb6AFNp1D/IIamIVfUBhGUPvhmHSwB+BaB9H9SV4yAQEuxIrP70hFV/ci ZdOu4JAz+W0VFYEU4DQpDNELHAdXWh4NvgMvutIdB+BlwTbCOyxl9PBe8KJM/hdhV/e6 6+mw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s6-v6si2331387plp.18.2018.04.16.13.47.05; Mon, 16 Apr 2018 13:47:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752310AbeDPUnf (ORCPT + 99 others); Mon, 16 Apr 2018 16:43:35 -0400 Received: from mx2.suse.de ([195.135.220.15]:57901 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751870AbeDPUne (ORCPT ); Mon, 16 Apr 2018 16:43:34 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 696A2ABB2; Mon, 16 Apr 2018 20:43:32 +0000 (UTC) Date: Mon, 16 Apr 2018 22:43:28 +0200 (CEST) From: Jiri Kosina To: Sasha Levin cc: 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 Subject: Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes In-Reply-To: <20180416203629.GO2341@sasha-vm> Message-ID: References: <20180415144248.GP2341@sasha-vm> <20180416093058.6edca0bb@gandalf.local.home> <20180416153031.GA5039@amd> <20180416155031.GX2341@sasha-vm> <20180416160608.GA7071@amd> <20180416161412.GZ2341@sasha-vm> <20180416170501.GB11034@amd> <20180416171607.GJ2341@sasha-vm> <20180416203629.GO2341@sasha-vm> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 16 Apr 2018, Sasha Levin wrote: > So I think that Linus's claim that users come first applies here as > well. If there's a user that cares about a particular feature being > broken, then we go ahead and fix his bug rather then ignoring him. So one extreme is fixing -stable *iff* users actually do report an issue. The other extreme is backporting everything that potentially looks like a potential fix of "something" (according to some arbitrary metric), pro-actively. The former voilates the "users first" rule, the latter has a very, very high risk of regressions. So this whole debate is about finding a compromise. My gut feeling always was that the statement in Documentation/process/stable-kernel-rules.rst is very reasonable, but making the process way more "aggresive" when backporting patches is breaking much of its original spirit for me. -- Jiri Kosina SUSE Labs