From: Andrew Morton <akpm@linux-foundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: <naoya.horiguchi@nec.com>, <linux-mm@kvack.org>,
<tony.luck@intel.com>, <linux-kernel@vger.kernel.org>,
<linmiaohe@huawei.com>
Subject: Re: [PATCH -next v2] mm: hwposion: support recovery from ksm_might_need_to_copy()
Date: Fri, 9 Dec 2022 16:50:15 -0800 [thread overview]
Message-ID: <20221209165015.7de5f7173c534c10875e10fb@linux-foundation.org> (raw)
In-Reply-To: <20221209072801.193221-1-wangkefeng.wang@huawei.com>
On Fri, 9 Dec 2022 15:28:01 +0800 Kefeng Wang <wangkefeng.wang@huawei.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?
next prev parent reply other threads:[~2022-12-10 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 2:15 [PATCH -next resend] " Kefeng Wang
2022-12-09 6:54 ` kernel test robot
2022-12-09 7:28 ` [PATCH -next v2] " Kefeng Wang
2022-12-10 0:50 ` Andrew Morton [this message]
2022-12-10 3:37 ` Kefeng Wang
2022-12-12 2:36 ` Miaohe Lin
2022-12-12 11:41 ` Kefeng Wang
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=20221209165015.7de5f7173c534c10875e10fb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.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