All of lore.kernel.org
 help / color / mirror / Atom feed
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>, David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH -next resend v3] mm: hwposion: support recovery from ksm_might_need_to_copy()
Date: Tue, 31 Jan 2023 16:32:04 -0800	[thread overview]
Message-ID: <20230131163204.2c511663bfece90d56121cc6@linux-foundation.org> (raw)
In-Reply-To: <20221213120523.141588-1-wangkefeng.wang@huawei.com>

On Tue, 13 Dec 2022 20:05:23 +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
> 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.


  parent reply	other threads:[~2023-02-01  0:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  3:05 [PATCH -next v3] mm: hwposion: support recovery from ksm_might_need_to_copy() Kefeng Wang
2022-12-13 11:33 ` kernel test robot
2022-12-13 12:05 ` [PATCH -next resend " Kefeng Wang
2022-12-16  1:47   ` HORIGUCHI NAOYA(堀口　直也)
2022-12-16  8:42     ` Kefeng Wang
2022-12-17  2:24     ` Miaohe Lin
2023-02-01  1:23       ` Kefeng Wang
2023-02-01  0:32   ` Andrew Morton [this message]
2023-02-01  1:33     ` 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=20230131163204.2c511663bfece90d56121cc6@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.