Return-Path: Date: Thu, 6 Dec 2018 12:13:28 +0100 From: Greg KH To: Vlastimil Babka Cc: Roman Gushchin , "stable@vger.kernel.org" , Yongqin Liu , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Kernel Team , Andrew Morton Subject: Re: [PATCH] mm: hide incomplete nr_indirectly_reclaimable in /proc/zoneinfo Message-ID: <20181206111328.GP19891@kroah.com> References: <20181030174649.16778-1-guro@fb.com> <20181129125228.GN3149@kroah.com> 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: On Thu, Nov 29, 2018 at 03:54:10PM +0100, Vlastimil Babka wrote: > On 11/29/18 1:52 PM, Greg KH wrote: > > On Tue, Oct 30, 2018 at 05:48:25PM +0000, Roman Gushchin wrote: > >> BTW, in 4.19+ the counter has been renamed and exported by > >> the commit b29940c1abd7 ("mm: rename and change semantics of > >> nr_indirectly_reclaimable_bytes"), so there is no such a problem > >> anymore. > >> > >> Cc: # 4.14.x-4.18.x > >> Fixes: 7aaf77272358 ("mm: don't show nr_indirectly_reclaimable in /proc/vmstat") > > ... > > > I do not see this patch in Linus's tree, do you? > > > > If not, what am I supposed to do with this? > > Yeah it wasn't probably clear enough, but this is stable-only patch, as > upstream avoided the (then-unknown) problem in 4.19 as part of a far > more intrusive series. As I've said in my previous reply to this thread, > I don't think we can backport that series to stable (e.g. it introduces > a set of new kmalloc caches that will suddenly appear in /proc/slabinfo) > so I think this is a case for exception from the stable rules. Ok, now queued up, thanks. greg k-h