From: zhenwei pi <pizhenwei@bytedance.com>
To: akpm@linux-foundation.org, naoya.horiguchi@nec.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
zhenwei pi <pizhenwei@bytedance.com>
Subject: [PATCH v2 0/1] mm/memory-failure: don't allow to unpoison hw corrupted page
Date: Wed, 8 Jun 2022 16:43:55 +0800 [thread overview]
Message-ID: <20220608084356.40894-1-pizhenwei@bytedance.com> (raw)
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 (1):
mm/memory-failure: don't allow to unpoison hw corrupted page
mm/memory-failure.c | 9 +++++++++
1 file changed, 9 insertions(+)
--
2.20.1
next reply other threads:[~2022-06-08 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 8:43 zhenwei pi [this message]
2022-06-08 8:43 ` [PATCH v2 1/1] mm/memory-failure: don't allow to unpoison hw corrupted page zhenwei pi
2022-06-08 9:30 ` David Hildenbrand
2022-06-10 5:06 ` zhenwei pi
2022-06-10 8:57 ` David Hildenbrand
2022-06-08 13:55 ` Miaohe Lin
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=20220608084356.40894-1-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@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).