[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190522145906.60c9e70ac0ed7ee3918a124c@linux-foundation.org>
Date: Wed, 22 May 2019 14:59:06 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Roman Gushchin <guro@...com>
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Kernel Team <Kernel-team@...com>,
"Johannes Weiner" <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Rik van Riel <riel@...riel.com>,
Shakeel Butt <shakeelb@...gle.com>,
Christoph Lameter <cl@...ux.com>,
Vladimir Davydov <vdavydov.dev@...il.com>,
"cgroups@...r.kernel.org" <cgroups@...r.kernel.org>,
Waiman Long <longman@...hat.com>
Subject: Re: [PATCH v5 0/7] mm: reparent slab memory on cgroup removal
On Wed, 22 May 2019 21:43:54 +0000 Roman Gushchin <guro@...com> wrote:
> Is this patchset good to go? Or do you have any remaining concerns?
>
> It has been carefully reviewed by Shakeel; and also Christoph and Waiman
> gave some attention to it.
>
> Since commit 172b06c32b94 ("mm: slowly shrink slabs with a relatively")
> has been reverted, the memcg "leak" problem is open again, and I've heard
> from several independent people and companies that it's a real problem
> for them. So it will be nice to close it asap.
>
> I suspect that the fix is too heavy for stable, unfortunately.
>
> Please, let me know if you have any issues that preventing you
> from pulling it into the tree.
I looked, and put it on ice for a while, hoping to hear from
mhocko/hannes. Did they look at the earlier versions?
Powered by blists - more mailing lists