From: Miaohe Lin <linmiaohe@huawei.com>
To: David Hildenbrand <david@redhat.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
zhenwei pi <pizhenwei@bytedance.com>, <naoya.horiguchi@nec.com>,
<akpm@linux-foundation.org>
Subject: Re: [PATCH v3 1/1] mm/memory-failure: don't allow to unpoison hw corrupted page
Date: Tue, 14 Jun 2022 10:16:16 +0800 [thread overview]
Message-ID: <844edb08-e145-0209-bf7a-60fb38503705@huawei.com> (raw)
In-Reply-To: <0fedf6f3-3ab3-e1d2-fd6e-3dbe8e92f06d@redhat.com>
On 2022/6/10 20:12, David Hildenbrand wrote:
>
> I really prefer just disabling the unpoisioning mechanism in case there
> is a real hw injected error.
IMHO, this would be a simple solution that also works on the arches that does not unmap
the kernel mapping when a page is hardware corrupted.
Thanks!
>
prev parent reply other threads:[~2022-06-14 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 11:46 [PATCH v3 0/1] " zhenwei pi
2022-06-10 11:46 ` [PATCH v3 1/1] " zhenwei pi
2022-06-10 12:12 ` David Hildenbrand
2022-06-14 0:22 ` zhenwei pi
2022-06-14 0:41 ` HORIGUCHI NAOYA(堀口 直也)
2022-06-14 2:16 ` Miaohe Lin [this message]
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=844edb08-e145-0209-bf7a-60fb38503705@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=pizhenwei@bytedance.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