Hi, This patchset tries to solve the issue among memory_hotplug, hugetlb and hwpoison. Based on the review over v2 by Miaohe (thank you!), 1/4 takes another approach to prevent hwpoisoned hugepages to be migrated (i.e. the corrupted data is accessed) in memory hotremove. In this patchset, memory hotplug handles hwpoison pages like below: - hwpoison pages should not prevent memory hotremove, - memory block with hwpoison pages should not be onlined. Any comments and feedbacks would be appreciated. Thanks, Naoya Horiguchi v1: https://lore.kernel.org/linux-mm/20220427042841.678351-1-naoya.horiguchi@xxxxxxxxx/T v2: https://lore.kernel.org/linux-mm/20220905062137.1455537-1-naoya.horiguchi@xxxxxxxxx/T --- Summary: Naoya Horiguchi (4): mm,hwpoison,hugetlb,memory_hotplug: hotremove memory section with hwpoisoned hugepage mm/hwpoison: move definitions of num_poisoned_pages_* to memory-failure.c mm/hwpoison: pass pfn to num_poisoned_pages_*() mm/hwpoison: introduce per-memory_block hwpoison counter arch/parisc/kernel/pdt.c | 5 ++-- drivers/base/memory.c | 36 +++++++++++++++++++++++++++++ include/linux/hugetlb.h | 4 ++-- include/linux/memory.h | 3 +++ include/linux/mm.h | 13 +++++++++++ include/linux/swapops.h | 24 ++------------------ mm/hugetlb.c | 4 ++-- mm/internal.h | 8 ------- mm/memory-failure.c | 59 +++++++++++++++++++++++++++--------------------- mm/sparse.c | 2 -- 10 files changed, 93 insertions(+), 65 deletions(-)
