From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:56723 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751629AbeDJUhv (ORCPT ); Tue, 10 Apr 2018 16:37:51 -0400 Date: Tue, 10 Apr 2018 22:37:49 +0200 From: Michal Hocko To: Sasha Levin Cc: Andrew Morton , Johannes Weiner , "stable@vger.kernel.org" Subject: Re: [PATCH] memcg: fix per_node_info cleanup Message-ID: <20180410203749.GW21835@dhcp22.suse.cz> References: <20180406100906.17790-1-mhocko@kernel.org> <20180410140132.GT21835@dhcp22.suse.cz> <20180410175510.GH2341@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180410175510.GH2341@sasha-vm> Sender: stable-owner@vger.kernel.org List-ID: On Tue 10-04-18 17:55:13, Sasha Levin wrote: > On Tue, Apr 10, 2018 at 04:01:32PM +0200, Michal Hocko wrote: > >On Tue 10-04-18 13:50:30, Sasha Levin wrote: > >> Hi, > >> > >> [This is an automated email] > >> > >> This commit has been processed because it contains a "Fixes:" tag, > >> fixing commit: 00f3ca2c2d66 mm: memcontrol: per-lruvec stats infrastructure. > > > >Yes and the changelog states conditions which are quite hard to achieve > >to have this patch in the stable tree. So I am not really convinced it > >is worth backporting even though the patch itself is trivial. > > Quite hard to achieve, but the changelog also indicated that this was > actually hit and is not just theoretical. Is there something that will > prevent this from happening on "real" workloads? Well, small allocations do not really fail and it would take to configure a really large NUMA system to achieve the same. So I am skeptical. -- Michal Hocko SUSE Labs