From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Kaitao Cheng <kaitao.cheng@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Zi Yan <ziy@nvidia.com>, Matthew Brost <matthew.brost@intel.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Rakie Kim <rakie.kim@sk.com>, Byungchul Park <byungchul@sk.com>,
Gregory Price <gourry@gourry.net>,
Ying Huang <ying.huang@linux.alibaba.com>,
Alistair Popple <apopple@nvidia.com>
Cc: Naoya Horiguchi <nao.horiguchi@gmail.com>,
Andi Kleen <ak@linux.intel.com>,
Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Kaitao Cheng <chengkaitao@kylinos.cn>
Subject: Re: [PATCH v2] mm/migrate: Avoid copying hwpoisoned folios during migration
Date: Tue, 7 Jul 2026 12:08:26 +0200 [thread overview]
Message-ID: <ea713b4c-b248-4191-9ed2-c9e2d0f83ad9@kernel.org> (raw)
In-Reply-To: <20260707090136.52904-1-kaitao.cheng@linux.dev>
On 7/7/26 11:01, Kaitao Cheng wrote:
> From: Kaitao Cheng <chengkaitao@kylinos.cn>
>
> The generic folio migration path can copy the source folio after it has
> been unmapped. For normal and THP folios this goes through
> move_to_new_folio(), then the filesystem or anonymous migration callback,
> and commonly reaches folio_mc_copy().
>
> folio_mc_copy() uses copy_mc_highpage(), but architectures without
> copy_mc_to_kernel support fall back to copy_highpage(). If the source
> folio already contains a hwpoisoned page, a normal copy can consume the
> poisoned memory and trigger a synchronous machine check.
Well, but the code can still race with memory_failure() IIUC, so it's not really
safe either?
--
Cheers,
David
next prev parent reply other threads:[~2026-07-07 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 9:01 [PATCH v2] mm/migrate: Avoid copying hwpoisoned folios during migration Kaitao Cheng
2026-07-07 10:08 ` David Hildenbrand (Arm) [this message]
2026-07-07 11:08 ` Huang, Ying
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=ea713b4c-b248-4191-9ed2-c9e2d0f83ad9@kernel.org \
--to=david@kernel.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=chengkaitao@kylinos.cn \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=kaitao.cheng@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=rakie.kim@sk.com \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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.