[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170308125102.GA27694@kroah.com>
Date: Wed, 8 Mar 2017 13:51:02 +0100
From: Greg KH <greg@...ah.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Stable tree <stable@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Hillf Danton <hillf.zj@...baba-inc.com>,
Johannes Weiner <hannes@...xchg.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Mel Gorman <mgorman@...e.de>, Michal Hocko <mhocko@...e.com>,
Minchan Kim <minchan@...nel.org>,
Trevor Cordes <trevor@...nopolis.ca>
Subject: Re: [PATCH stable-4.9 0/2] mm: follow up oom fixes for 32b
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
Powered by blists - more mailing lists