From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: <tony.luck@intel.com>, <linux-kernel@vger.kernel.org>,
HORIGUCHI NAOYA <naoya.horiguchi@nec.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH -next v2] mm: hwposion: support recovery from ksm_might_need_to_copy()
Date: Mon, 12 Dec 2022 19:41:32 +0800 [thread overview]
Message-ID: <d7a0165c-39f6-87ce-f2ec-1f670541147a@huawei.com> (raw)
In-Reply-To: <342f4d3f-7347-1615-7d63-cbdef4872629@huawei.com>
On 2022/12/12 10:36, Miaohe Lin wrote:
> On 2022/12/9 15:28, Kefeng Wang 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.
...
>
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 908a529bca12..d479811bc311 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -1767,7 +1767,7 @@ static int unuse_pte(struct vm_area_struct *vma, pmd_t *pmd,
>
> swapcache = page;
> page = ksm_might_need_to_copy(page, vma, addr);
> - if (unlikely(!page))
> + if (IS_ERR_OR_NULL(page))
> IMHO, it might be better to install a hwpoison entry here. Or later swapoff ops will trigger
> the uncorrectable error again?
Thanks for you suggestion, will do in v3.
> Thanks,
> Miaohe Lin
>
prev parent reply other threads:[~2022-12-12 11:41 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
2022-12-10 3:37 ` Kefeng Wang
2022-12-12 2:36 ` Miaohe Lin
2022-12-12 11:41 ` Kefeng Wang [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=d7a0165c-39f6-87ce-f2ec-1f670541147a@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=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 \
/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