[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230131163204.2c511663bfece90d56121cc6@linux-foundation.org>
Date: Tue, 31 Jan 2023 16:32:04 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kefeng Wang <wangkefeng.wang@...wei.com>
Cc: <naoya.horiguchi@....com>, <linux-mm@...ck.org>,
<tony.luck@...el.com>, <linux-kernel@...r.kernel.org>,
<linmiaohe@...wei.com>, David Hildenbrand <david@...hat.com>
Subject: Re: [PATCH -next resend v3] mm: hwposion: support recovery from
ksm_might_need_to_copy()
On Tue, 13 Dec 2022 20:05:23 +0800 Kefeng Wang <wangkefeng.wang@...wei.com> wrote:
> When the kernel copy a page from ksm_might_need_to_copy(), but runs
> into an uncorrectable error, it will crash since poisoned page is
> consumed by kernel, this is similar to Copy-on-write poison recovery,
> When an error is detected during the page copy, return VM_FAULT_HWPOISON
> in do_swap_page(), and install a hwpoison entry in unuse_pte() when
> swapoff, which help us to avoid system crash. Note, memory failure on
> a KSM page will be skipped, but still call memory_failure_queue() to
> be consistent with general memory failure process.
I believe we're awaiting a v4 of this?
Did we consider a -stable backport? "kernel crash" sounds undesirable...
Can we identify a Fixes: target for this?
Thanks.
Powered by blists - more mailing lists