From: akpm@linux-foundation.org
To: linux-mm@kvack.org, akpm@linux-foundation.org,
ldufour@linux.vnet.ibm.com, avagin@openvz.org,
bsingharora@gmail.com, glommer@openvz.org,
n-horiguchi@ah.jp.nec.com, vdavydov.dev@gmail.com
Subject: [patch 01/15] mm: skip HWPoisoned pages when onlining pages
Date: Thu, 30 Nov 2017 14:15:11 -0800 [thread overview]
Message-ID: <5a2082ef.O5KuTYIgAA5wXBLf%akpm@linux-foundation.org> (raw)
From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Subject: mm: skip HWPoisoned pages when onlining pages
b023f46813cd ("memory-hotplug: skip HWPoisoned page when offlining pages")
skipped the HWPoisoned pages when offlining pages, but this should be
skipped when onlining the pages too.
n-horiguchi@ah.jp.nec.com said:
: If I read correctly, to "skip HWPoiosned page" in commit b023f46813cd
: means that we skip the page status check for hwpoisoned pages *not* to
: prevent memory offlining for memblocks with hwpoisoned pages. That
: means that hwpoisoned pages can be offlined.
:
: And another reason to clear PageReserved is that we could reuse the
: hwpoisoned page after onlining back with replacing the broken DIMM. In
: this usecase, we first do unpoisoning to clear PageHWPoison, but it
: doesn't work if PageReserved is set. My simple testing shows the BUG
: below in unpoisoning (without the ClearPageReserved):
:
: Unpoison: Software-unpoisoned page 0x18000
: BUG: Bad page state in process page-types pfn:18000
: page:ffffda5440600000 count:0 mapcount:0 mapping: (null) index:0x70006b599
: flags: 0x1fffc00004081a(error|uptodate|dirty|reserved|swapbacked)
: raw: 001fffc00004081a 0000000000000000 000000070006b599 00000000ffffffff
: raw: dead000000000100 dead000000000200 0000000000000000 0000000000000000
: page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set
: bad because of flags: 0x800(reserved)
Link: http://lkml.kernel.org/r/1493130472-22843-3-git-send-email-ldufour@linux.vnet.ibm.com
Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Andrey Vagin <avagin@openvz.org>
Cc: Glauber Costa <glommer@openvz.org>
Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: Balbir Singh <bsingharora@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory_hotplug.c | 4 ++++
1 file changed, 4 insertions(+)
diff -puN mm/memory_hotplug.c~mm-skip-hwpoisoned-pages-when-onlining-pages mm/memory_hotplug.c
--- a/mm/memory_hotplug.c~mm-skip-hwpoisoned-pages-when-onlining-pages
+++ a/mm/memory_hotplug.c
@@ -696,6 +696,10 @@ static int online_pages_range(unsigned l
if (PageReserved(pfn_to_page(start_pfn)))
for (i = 0; i < nr_pages; i++) {
page = pfn_to_page(start_pfn + i);
+ if (PageHWPoison(page)) {
+ ClearPageReserved(page);
+ continue;
+ }
(*online_page_callback)(page);
onlined_pages++;
}
_
--
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>
reply other threads:[~2017-11-30 22:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5a2082ef.O5KuTYIgAA5wXBLf%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=avagin@openvz.org \
--cc=bsingharora@gmail.com \
--cc=glommer@openvz.org \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=vdavydov.dev@gmail.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