[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221209165015.7de5f7173c534c10875e10fb@linux-foundation.org>
Date: Fri, 9 Dec 2022 16:50:15 -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>
Subject: Re: [PATCH -next v2] mm: hwposion: support recovery from
ksm_might_need_to_copy()
On Fri, 9 Dec 2022 15:28:01 +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,
> 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.
Thanks. Sorry, lots of paperwork and bureaucracy:
Is a copy of the oops(?) output available?
Did someone else report this? If so, is a Reported-by available for
that? And a Link: for the Reported-by:, which is a coming thing.
Can we identify a Fixes: target?
Is a cc:stable appropriate?
Powered by blists - more mailing lists