From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6FBE4C3A5A3 for ; Tue, 27 Aug 2019 18:39:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 38DB0206BF for ; Tue, 27 Aug 2019 18:39:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="ERL0kigP"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="wMTir3CH" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730465AbfH0Sjq (ORCPT ); Tue, 27 Aug 2019 14:39:46 -0400 Received: from new4-smtp.messagingengine.com ([66.111.4.230]:50555 "EHLO new4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729779AbfH0Sjq (ORCPT ); Tue, 27 Aug 2019 14:39:46 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 101C528AD; Tue, 27 Aug 2019 14:39:45 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 27 Aug 2019 14:39:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=2Pi2UrTYWIZeSLhHDsmgNc73uGU Eowqv9oRu+ZwsHGA=; b=ERL0kigPYO3OOz4tGQ+vEqkqh0JtqzICMMQfqdWbcU/ rytJcRaMGrU/T8owYvdVPhUKoDWhD0/ZOr1Z5wHQJE4Ug5/TmRzTt9/72pfzgiuL Du1v8YcF7vi673FsOfHS3CwrD8BfytsPXZ9rD/wJe94ok9QIYzCYWXR7DkiwCU+T cV7GGZDxvYZilkzclYwbHDf0a2VdjdCZJAOfJmPhaSHd7Yy1qGF3j1/edzsYmCHx 2DK47P8o90y3AcG9b8cWDMNx+XtBlahTB7SptqEo+PDdnYp+1uBj4YlurE/1aSjD PmGDvqUtiNwcDXRucyXs/4vxz96WbU2QwLrkUr3ue8w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=2Pi2Ur TYWIZeSLhHDsmgNc73uGUEowqv9oRu+ZwsHGA=; b=wMTir3CHsmW0knAj4jGavl VA3aikjJIy/f6GBK9UNZuaKk7Whb35zv9Tk7sPLWnTsxGrI/w9jAcAVbOeOqD750 He9Pkdwp7mNCVN8qZkuPyI0wdsF6fDD5JzpVr4UpietVo1Y8/i8mJp18D3vHWjp0 ixBpcqJ6z8LZs5sO64y3Tq0eRdmn5Pnx2SdtHcU10vOqzSqDsmmDnkua58OkiGfG ZOPrWiV2J2joUvQdfOpEItP3AXgoZ0Y2O6/rdVMJwsr3K180qg3c4xztZP35Yr+k Vqw3ZcjK5GLwNwr1XwKnIfqUg1+UXhYgQDMur9W1zUXeq4WHy1Ju17TUrV8UY+Sw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudehkedgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuffhomhgrihhnpehkvghrnhgvlh drohhrghenucfkphepkeefrdekiedrkeelrddutdejnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehgrhgvgheskhhrohgrhhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id ABAA580063; Tue, 27 Aug 2019 14:39:42 -0400 (EDT) Date: Tue, 27 Aug 2019 20:39:40 +0200 From: Greg KH To: Sasha Levin , Michal Hocko Cc: Thomas Backlund , Andrew Morton , Roman Gushchin , "linux-mm@kvack.org" , Johannes Weiner , "linux-kernel@vger.kernel.org" , Kernel Team , "stable@vger.kernel.org" , Yafang Shao Subject: Re: [PATCH] Partially revert "mm/memcontrol.c: keep local VM counters in sync with the hierarchical ones" Message-ID: <20190827183940.GA2924@kroah.com> References: <20190817004726.2530670-1-guro@fb.com> <20190817063616.GA11747@kroah.com> <20190817191518.GB11125@castle> <20190824125750.da9f0aac47cc0a362208f9ff@linux-foundation.org> <20190827141016.GH7538@dhcp22.suse.cz> <20190827170618.GC21369@kroah.com> <20190827173950.GJ7538@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190827173950.GJ7538@dhcp22.suse.cz> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Tue, Aug 27, 2019 at 07:39:50PM +0200, Michal Hocko wrote: > On Tue 27-08-19 19:06:18, Greg KH wrote: > > On Tue, Aug 27, 2019 at 04:10:16PM +0200, Michal Hocko wrote: > > > On Sat 24-08-19 23:23:07, Thomas Backlund wrote: > > > > Den 24-08-2019 kl. 22:57, skrev Andrew Morton: > > > > > On Sat, 17 Aug 2019 19:15:23 +0000 Roman Gushchin wrote: > > > > > > > > > > > > > Fixes: 766a4c19d880 ("mm/memcontrol.c: keep local VM counters in sync with the hierarchical ones") > > > > > > > > Signed-off-by: Roman Gushchin > > > > > > > > Cc: Yafang Shao > > > > > > > > Cc: Johannes Weiner > > > > > > > > --- > > > > > > > > mm/memcontrol.c | 8 +++----- > > > > > > > > 1 file changed, 3 insertions(+), 5 deletions(-) > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is not the correct way to submit patches for inclusion in the > > > > > > > stable kernel tree. Please read: > > > > > > > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > > > > > > > for how to do this properly. > > > > > > > > > > > > Oh, I'm sorry, will read and follow next time. Thanks! > > > > > > > > > > 766a4c19d880 is not present in 5.2 so no -stable backport is needed, yes? > > > > > > > > > > > > > Unfortunately it got added in 5.2.7, so backport is needed. > > > > > > yet another example of patch not marked for stable backported to the > > > stable tree. yay... > > > > If you do not want autobot to pick up patches for specific > > subsystems/files, just let us know and we will add them to the > > blacklist. > > Done that on several occasions over last year and so. I always get "yep > we are going to black list" and whoops and we are back there with > patches going to stable like nothing happened. We've been through this > discussion so many times I am tired of it and to be honest I simply do > not care anymore. > > I will keep encouraging people to mark patches for stable but I do not > give a wee bit about any reports for the stable tree. Nor do I care > whether something made it in and we should be careful to mark another > patch for stable as a fixup like this one. Sasha, can you add these to the blacklist for autosel? thanks, greg k-h