From: Vasily Averin Subject: Re: [PATCH memcg v3 3/3] memcg: prohibit unconditional exceeding the limit of dying tasks Date: Thu, 28 Oct 2021 10:22:56 +0300 Message-ID: References: <8f5cebbb-06da-4902-91f0-6566fc4b4203@virtuozzo.com> <20211027153608.9910f7db99d5ef574045370e@linux-foundation.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtuozzo.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/y06wyIaTQk/vqnWTXXrbA0/17cWwIbbEVGj8aQ97gw=; b=v0E1eKyk5HkI9KAhSRzN5tvx7lbiK4uS9uNhLCAGMXtyZ39nTwFO6n93BCM75aEYeizhPiQwNeBAKbAJE/VbQkGLN+g699ubbOAQmQHXiS64YmlC+msidD4htb+7ITDU4j7Jbhhf/wcicsPqCRS78YUaYE0PrTHOjAp7l44JAeg= In-Reply-To: <20211027153608.9910f7db99d5ef574045370e-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> Content-Language: en-US List-ID: Content-Type: text/plain; charset="us-ascii" To: Andrew Morton , Michal Hocko Cc: Johannes Weiner , Vladimir Davydov , Roman Gushchin , Uladzislau Rezki , Vlastimil Babka , Shakeel Butt , Mel Gorman , Tetsuo Handa , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kernel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org, Greg Kroah-Hartman On 28.10.2021 01:36, Andrew Morton wrote: > On Mon, 25 Oct 2021 11:36:41 +0200 Michal Hocko wrote: > >> My view on stable backport is similar to the previous patch. If we want >> to have it there then let's wait for some time to see whether there are >> any fallouts as this patch depends on the PF_OOM change. > > It's strange that [1/3] doesn't have cc:stable, but [2/3] and [3/3] do > not. What is the thinking here? My fault, I missed it. All 3 patches should be backported, I did it already to stables kernels since 4.4 and I'm ready to submit it in demand. > I expect we'd be OK with merging these into 5.16-rc1. This still gives > another couple of months in -rc to shake out any problems. But I > suspect the -stable maintainers will merge and release the patches > before they are released in 5.16. > > In which case an alternative would be not to mark these patches > cc:stable and to somehow remember to ask the -stable maintainers to > merge them after 5.16 has been on the streets for a suitable period. > > Greg, thoughts? If you wish I can remind Greg in a month or even after 5.17 release. Thank you, Vasily Averin