From: Roman Gushchin <guro@fb.com>
To: <gregkh@linuxfoundation.org>
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: Mon, 14 May 2018 11:46:00 +0100 [thread overview]
Message-ID: <20180514104553.GA28956@castle> (raw)
In-Reply-To: <1526132159220203@kroah.com>
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 <stable@vger.kernel.org>.
>
> 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
next prev parent reply other threads:[~2018-05-14 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 13:35 FAILED: patch "[PATCH] mm: treat indirectly reclaimable memory as free in overcommit" failed to apply to 4.16-stable tree gregkh
2018-05-14 10:46 ` Roman Gushchin [this message]
2018-10-11 14:27 ` Greg KH
2018-10-11 21:04 ` Roman Gushchin
2018-10-16 14:01 ` 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=20180514104553.GA28956@castle \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=mhocko@suse.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.