[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220614043830.99607-1-pizhenwei@bytedance.com>
Date: Tue, 14 Jun 2022 12:38:28 +0800
From: zhenwei pi <pizhenwei@...edance.com>
To: akpm@...ux-foundation.org, naoya.horiguchi@....com
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, david@...hat.com,
linmiaohe@...wei.com, zhenwei pi <pizhenwei@...edance.com>
Subject: [PATCH v4 0/2] mm/memory-failure: don't allow to unpoison hw corrupted page
v3 -> v4:
- Add debug entry "hwpoisoned-pages" to show the number of hwpoisoned
pages.
- Disable unpoison when a read HW memory failure occurs.
v2 -> v3:
- David pointed out that virt_to_kpte() is broken(no pmd_large() test
on a PMD), so drop this API in this patch, walk kmap instead.
v1 -> v2:
- this change gets protected by mf_mutex
- use -EOPNOTSUPP instead of -EPERM
v1:
- check KPTE to avoid to unpoison hardware corrupted page
zhenwei pi (2):
mm/memory-failure: introduce "hwpoisoned-pages" entry
mm/memory-failure: disable unpoison once hw error happens
Documentation/vm/hwpoison.rst | 7 ++++++-
mm/hwpoison-inject.c | 25 ++++++++++++++++++++++++-
mm/memory-failure.c | 1 +
3 files changed, 31 insertions(+), 2 deletions(-)
--
2.20.1
Powered by blists - more mailing lists