From: Naoya Horiguchi <nao.horiguchi@gmail.com>
To: linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@suse.com>, Ding Hui <dinghui@sangfor.com.cn>,
Tony Luck <tony.luck@intel.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/6] mm/hwpoison: fix unpoison_memory()
Date: Mon, 14 Jun 2021 11:12:06 +0900 [thread overview]
Message-ID: <20210614021212.223326-1-nao.horiguchi@gmail.com> (raw)
Hi,
This patchset is suggesting to adjust unpoison_memory() to the new way of
isolation and refcounting of hwpoisoned pages.
As mentioned in [1], NR_FREE_PAGES is incremented via newly added function
undoing take_page_off_buddy(), so the counter is consistent with this series.
It depends on some other hwpoison-related patches (not mainlined but in linux-mm),
so I listed the dependencies here:
- mm/hwpoison: do not lock page again when me_huge_page() successfully recovers
- mm/memory-failure: make sure wait for page writeback in memory_failure
- mm,hwpoison: make get_hwpoison_page() call get_any_page()
- mm,hwpoison: fix race with hugetlb page allocation
- mm,hwpoison: Send SIGBUS with error virutal address
- mm,hwpoison: Return -EHWPOISON to denote that the page has already been poisoned
- mm/memory-failure: Use a mutex to avoid memory_failure() races
Or GitHub branch I pushed for easy patch access might be helpful for reviewers.
git fetch https://github.com/nhoriguchi/linux hwpoison
[1] https://lore.kernel.org/linux-mm/20210527003436.GA3543069@hori.linux.bs1.fc.nec.co.jp/
Thanks,
Naoya Horiguchi
---
Summary:
Naoya Horiguchi (6):
mm/hwpoison: mf_mutex for soft offline and unpoison
mm/hwpoison: remove race consideration
mm/hwpoison: introduce MF_MSG_PAGETABLE
mm/hwpoison: remove MF_MSG_BUDDY_2ND and MF_MSG_POISONED_HUGE
mm/hwpoison: make some kernel pages handlable
mm/hwpoison: fix unpoison_memory()
include/linux/mm.h | 4 +-
include/linux/page-flags.h | 4 ++
include/ras/ras_event.h | 3 +-
mm/memory-failure.c | 176 +++++++++++++++++++++++++--------------------
mm/page_alloc.c | 19 +++++
5 files changed, 126 insertions(+), 80 deletions(-)
next reply other threads:[~2021-06-14 2:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 2:12 Naoya Horiguchi [this message]
2021-06-14 2:12 ` [PATCH v1 1/6] mm/hwpoison: mf_mutex for soft offline and unpoison Naoya Horiguchi
2021-06-15 11:41 ` Ding Hui
2021-06-14 2:12 ` [PATCH v1 2/6] mm/hwpoison: remove race consideration Naoya Horiguchi
2021-06-15 12:57 ` Ding Hui
[not found] ` <20210616001141.GA1924716@hori.linux.bs1.fc.nec.co.jp>
2021-06-16 0:40 ` Ding Hui
2021-06-14 2:12 ` [PATCH v1 3/6] mm/hwpoison: introduce MF_MSG_PAGETABLE Naoya Horiguchi
2021-06-14 3:06 ` Matthew Wilcox
2021-06-14 2:12 ` [PATCH v1 4/6] mm/hwpoison: remove MF_MSG_BUDDY_2ND and MF_MSG_POISONED_HUGE Naoya Horiguchi
2021-06-14 2:12 ` [PATCH v1 5/6] mm/hwpoison: make some kernel pages handlable Naoya Horiguchi
2021-07-28 10:59 ` Ding Hui
2021-06-14 2:12 ` [PATCH v1 6/6] mm/hwpoison: fix unpoison_memory() Naoya Horiguchi
2021-06-17 10:00 ` Ding Hui
[not found] ` <20210618083625.GA2215283@hori.linux.bs1.fc.nec.co.jp>
2021-06-19 12:22 ` Ding Hui
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=20210614021212.223326-1-nao.horiguchi@gmail.com \
--to=nao.horiguchi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=david@redhat.com \
--cc=dinghui@sangfor.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=tony.luck@intel.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).