Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: Re: [PATCH v3 1/1] mm/memory-failure: don't allow to unpoison hw
 corrupted page
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>
References: <20220610114646.162764-1-pizhenwei@bytedance.com>
 <20220610114646.162764-2-pizhenwei@bytedance.com>
 <0fedf6f3-3ab3-e1d2-fd6e-3dbe8e92f06d@redhat.com>
From:   Miaohe Lin <linmiaohe@huawei.com>
Message-ID: <844edb08-e145-0209-bf7a-60fb38503705@huawei.com>
Date:   Tue, 14 Jun 2022 10:16:16 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <0fedf6f3-3ab3-e1d2-fd6e-3dbe8e92f06d@redhat.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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!

>