From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752968AbdCHMvh (ORCPT <rfc822;w@1wt.eu>);
        Wed, 8 Mar 2017 07:51:37 -0500
Received: from out1-smtp.messagingengine.com ([66.111.4.25]:45378 "EHLO
        out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1750770AbdCHMvd (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 8 Mar 2017 07:51:33 -0500
X-ME-Sender: <xms:PP6_WADN4ZQxA9mPMfE8lkgdJf3BYjC8JbcH7SiFKywcbTA9OQUHbg>
X-Sasl-enc: 3MPU7zZhvx0W1kE1mVXOql5oy6IBsVtLw5kVU69hH6k2 1488977468
Date: Wed, 8 Mar 2017 13:51:02 +0100
From: Greg KH <greg@kroah.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Stable tree <stable@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org,
        Andrew Morton <akpm@linux-foundation.org>,
        Hillf Danton <hillf.zj@alibaba-inc.com>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Mel Gorman <mgorman@suse.de>, Michal Hocko <mhocko@suse.com>,
        Minchan Kim <minchan@kernel.org>, Trevor Cordes <trevor@tecnopolis.ca>
Subject: Re: [PATCH stable-4.9 0/2] mm: follow up oom fixes for 32b
Message-ID: <20170308125102.GA27694@kroah.com>
References: <20170228151108.20853-1-mhocko@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170228151108.20853-1-mhocko@kernel.org>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Feb 28, 2017 at 04:11:06PM +0100, Michal Hocko wrote:
> Hi,
> later in the 4.10 release cycle it turned out that b4536f0c829c ("mm,
> memcg: fix the active list aging for lowmem requests when memcg is
> enabled") was not sufficient to fully close the regression introduced by
> f8d1a31163fc ("mm: consider whether to decivate based on eligible zones
> inactive ratio") [1]. mmotm tree behaved properly and it turned out the
> Linus tree was missing 71ab6cfe88dc ("mm, vmscan: consider eligible
> zones in get_scan_count") merged in 4.11 merge window. The patch heavily
> depends on 4a9494a3d827 ("mm, vmscan: cleanup lru size claculations")
> which has been backported as well (patch 1).
> 
> Please add these two to 4.9+ trees (they should apply to 4.10 as they
> are).  4.8 tree will need them as well but I do not see this stable tree
> being maintained.

For 4.10-stable I needed both of your backports, many thanks for them.

greg k-h