From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org
Subject: [RFC 1/2] mm: Uncharge poisoned pages
Date: Thu, 20 Apr 2017 11:26:01 +0200 [thread overview]
Message-ID: <1492680362-24941-2-git-send-email-ldufour@linux.vnet.ibm.com> (raw)
In-Reply-To: <1492680362-24941-1-git-send-email-ldufour@linux.vnet.ibm.com>
When page are poisoned, they should be uncharged from the root memory
cgroup.
Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
---
mm/memory-failure.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index 27f7210e7fab..00bd39d3d4cb 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -530,6 +530,7 @@ static const char * const action_page_types[] = {
static int delete_from_lru_cache(struct page *p)
{
if (!isolate_lru_page(p)) {
+ memcg_kmem_uncharge(p, 0);
/*
* Clear sensible page flags, so that the buddy system won't
* complain when the page is unpoison-and-freed.
--
2.7.4
--
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 prev parent reply other threads:[~2017-04-20 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 9:26 [RFC 0/2] BUG raised when onlining HWPoisoned page Laurent Dufour
2017-04-20 9:26 ` Laurent Dufour [this message]
2017-04-24 9:05 ` [RFC 1/2] mm: Uncharge poisoned pages Naoya Horiguchi
2017-04-24 13:15 ` Laurent Dufour
2017-04-20 9:26 ` [RFC 2/2] mm: skip HWPoisoned pages when onlining pages Laurent Dufour
2017-04-25 8:00 ` Naoya Horiguchi
2017-04-25 14:16 ` Laurent Dufour
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=1492680362-24941-2-git-send-email-ldufour@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
/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).