From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:58364 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752011AbeENKqa (ORCPT ); Mon, 14 May 2018 06:46:30 -0400 Date: Mon, 14 May 2018 11:46:00 +0100 From: Roman Gushchin To: CC: , , , , , Subject: Re: FAILED: patch "[PATCH] mm: treat indirectly reclaimable memory as free in overcommit" failed to apply to 4.16-stable tree Message-ID: <20180514104553.GA28956@castle> References: <1526132159220203@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <1526132159220203@kroah.com> Sender: stable-owner@vger.kernel.org List-ID: On Sat, May 12, 2018 at 03:35:59PM +0200, gregkh@linuxfoundation.org wrote: > > 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 commit > id to . > > thanks, > > greg k-h Hi, Greg! 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 overcommit logic f1782c9bc547 dcache: account external names as indirectly reclaimable memory 034ebf65c3c2 mm: treat indirectly reclaimable memory as available in MemAvailable eb59254608bc mm: introduce NR_INDIRECTLY_RECLAIMABLE_BYTES It should be backported as a whole. It applies cleanly on 4.16-stable, and with a minor trivial adjustment to 4.14-stable. Thank you! Roman