From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-sn1nam02on0133.outbound.protection.outlook.com ([104.47.36.133]:42144 "EHLO NAM02-SN1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751624AbeDJRzP (ORCPT ); Tue, 10 Apr 2018 13:55:15 -0400 From: Sasha Levin To: Michal Hocko CC: Andrew Morton , Johannes Weiner , "stable@vger.kernel.org" Subject: Re: [PATCH] memcg: fix per_node_info cleanup Date: Tue, 10 Apr 2018 17:55:13 +0000 Message-ID: <20180410175510.GH2341@sasha-vm> References: <20180406100906.17790-1-mhocko@kernel.org> <20180410140132.GT21835@dhcp22.suse.cz> In-Reply-To: <20180410140132.GT21835@dhcp22.suse.cz> Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-ID: <1A5AAAD75DA05645A1E34CD5F4A5D816@namprd21.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: stable-owner@vger.kernel.org List-ID: 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 infrastruct= ure. > >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?=