[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a4495506-2dcf-922a-1b77-e915214dd041@suse.cz>
Date: Thu, 29 Nov 2018 15:54:10 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Greg KH <gregkh@...uxfoundation.org>, Roman Gushchin <guro@...com>
Cc: "stable@...r.kernel.org" <stable@...r.kernel.org>,
Yongqin Liu <yongqin.liu@...aro.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Kernel Team <Kernel-team@...com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] mm: hide incomplete nr_indirectly_reclaimable in
/proc/zoneinfo
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: <stable@...r.kernel.org> # 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.
Vlastimil
> confused,
>
> greg k-h
>
Powered by blists - more mailing lists