From: Michal Hocko <mhocko@kernel.org>
To: Stable tree <stable@vger.kernel.org>
Cc: 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: [PATCH stable-4.9 0/2] mm: follow up oom fixes for 32b
Date: Tue, 28 Feb 2017 16:11:06 +0100 [thread overview]
Message-ID: <20170228151108.20853-1-mhocko@kernel.org> (raw)
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.
[1] http://lkml.kernel.org/r/20170201032928.5d58a7c5@pog.tecnopolis.ca
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-02-28 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 15:11 Michal Hocko [this message]
2017-02-28 15:11 ` [PATCH stable-4.9 1/2] mm, vmscan: cleanup lru size claculations Michal Hocko
2017-02-28 15:11 ` [PATCH stable-4.9 2/2] mm, vmscan: consider eligible zones in get_scan_count Michal Hocko
2017-03-06 18:00 ` MegaBrutal
2017-03-07 14:14 ` Michal Hocko
2017-03-08 12:51 ` [PATCH stable-4.9 0/2] mm: follow up oom fixes for 32b Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170228151108.20853-1-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trevor@tecnopolis.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).