From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-00082601.pphosted.com ([67.231.145.42]:32816 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726040AbeJLEd1 (ORCPT ); Fri, 12 Oct 2018 00:33:27 -0400 From: Roman Gushchin To: Greg KH CC: "akpm@linux-foundation.org" , "hannes@cmpxchg.org" , "mhocko@suse.com" , "torvalds@linux-foundation.org" , "viro@zeniv.linux.org.uk" , "stable@vger.kernel.org" Subject: Re: FAILED: patch "[PATCH] mm: treat indirectly reclaimable memory as free in overcommit" failed to apply to 4.16-stable tree Date: Thu, 11 Oct 2018 21:04:17 +0000 Message-ID: <20181011210409.GA4320@tower.DHCP.thefacebook.com> References: <1526132159220203@kroah.com> <20180514104553.GA28956@castle> <20181011142746.GE9507@kroah.com> In-Reply-To: <20181011142746.GE9507@kroah.com> Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-ID: <6D57218D09813747AEE4674E8DB581AB@namprd15.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: stable-owner@vger.kernel.org List-ID: On Thu, Oct 11, 2018 at 04:27:46PM +0200, Greg KH wrote: > On Mon, May 14, 2018 at 11:46:00AM +0100, Roman Gushchin wrote: > > On Sat, May 12, 2018 at 03:35:59PM +0200, gregkh@linuxfoundation.org wr= ote: > > >=20 > > > The patch below does not apply to the 4.16-stable tree. > > > If someone wants it applied there, or to any other stable or longterm > > > tree, then please email the backport, including the original git comm= it > > > id to . > > >=20 > > > thanks, > > >=20 > > > greg k-h > >=20 > > Hi, Greg! > >=20 > > This patch is a part of the following patchset: > > 7aaf77272358 mm: don't show nr_indirectly_reclaimable in /proc/vmstat > > d79f7aa496fc mm: treat indirectly reclaimable memory as free in overcom= mit logic > > f1782c9bc547 dcache: account external names as indirectly reclaimable m= emory > > 034ebf65c3c2 mm: treat indirectly reclaimable memory as available in Me= mAvailable > > eb59254608bc mm: introduce NR_INDIRECTLY_RECLAIMABLE_BYTES > >=20 > > It should be backported as a whole. It applies cleanly on 4.16-stable, > > and with a minor trivial adjustment to 4.14-stable. >=20 > Sorry for the long delay, digging out of my stable backlog... >=20 > Anyway, is this still needed for 4.14-stable? There is a security issue, which these patches are closing. It allows to ca= use a system-wide memory allocation failure, if overcommit logic is enabled and it's possible to create negative dentries (e.g. asking httpd for non-existi= ng files). The issue is very old and exists in most stable branches, so Idk ho= w bad is to leave it open in 4.14. Anyway, please, let me know if I can help somehow. Thanks!