From: Andrew Morton <akpm@linux-foundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: <linux-mm@kvack.org>, Tony Luck <tony.luck@intel.com>,
Miaohe Lin <linmiaohe@huawei.com>, <nao.horiguchi@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
Muchun Song <muchun.song@linux.dev>,
Benjamin LaHaise <bcrl@kvack.org>, <jglisse@redhat.com>,
Jiaqi Yan <jiaqiyan@google.com>, Hugh Dickins <hughd@google.com>,
Vishal Moola <vishal.moola@gmail.com>,
Alistair Popple <apopple@nvidia.com>,
Jane Chu <jane.chu@oracle.com>,
Oscar Salvador <osalvador@suse.de>,
Lance Yang <ioworker0@gmail.com>
Subject: Re: [PATCH v5 0/6] mm: migrate: support poison recover from migrate folio
Date: Wed, 26 Jun 2024 13:04:27 -0700 [thread overview]
Message-ID: <20240626130427.2124681ea725b306de4d103d@linux-foundation.org> (raw)
In-Reply-To: <20240626085328.608006-1-wangkefeng.wang@huawei.com>
On Wed, 26 Jun 2024 16:53:22 +0800 Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
> The folio migration is widely used in kernel, memory compaction, memory
> hotplug, soft offline page, numa balance, memory demote/promotion, etc,
> but once access a poisoned source folio when migrating, the kernel will
> panic.
Is there some simple fixup which we can prepare for -stable kernels
which will avoid this panic?
next prev parent reply other threads:[~2024-06-26 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 8:53 Kefeng Wang
2024-06-26 8:53 ` [PATCH v5 1/6] mm: move memory_failure_queue() into copy_mc_[user]_highpage() Kefeng Wang
2024-06-26 8:53 ` [PATCH v5 2/6] mm: add folio_mc_copy() Kefeng Wang
2024-06-26 8:53 ` [PATCH v5 3/6] mm: migrate: split folio_migrate_mapping() Kefeng Wang
2024-06-26 8:53 ` [PATCH v5 4/6] mm: migrate: support poisoned recover from migrate folio Kefeng Wang
2024-06-26 8:53 ` [PATCH v5 5/6] fs: hugetlbfs: support poisoned recover from hugetlbfs_migrate_folio() Kefeng Wang
2024-06-26 8:53 ` [PATCH v5 6/6] mm: migrate: remove folio_migrate_copy() Kefeng Wang
2024-06-26 20:04 ` Andrew Morton [this message]
2024-06-27 1:06 ` [PATCH v5 0/6] mm: migrate: support poison recover from migrate folio 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=20240626130427.2124681ea725b306de4d103d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=bcrl@kvack.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=ioworker0@gmail.com \
--cc=jane.chu@oracle.com \
--cc=jglisse@redhat.com \
--cc=jiaqiyan@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=tony.luck@intel.com \
--cc=vishal.moola@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
/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