From: Wupeng Ma <mawupeng1@huawei.com>
To: <akpm@linux-foundation.org>, <david@redhat.com>,
<osalvador@suse.de>, <nao.horiguchi@gmail.com>,
<linmiaohe@huawei.com>, <mhocko@suse.com>
Cc: <mawupeng1@huawei.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/3] mm: memory_failure: unmap poisoned filio during migrate properly
Date: Mon, 17 Feb 2025 09:43:26 +0800 [thread overview]
Message-ID: <20250217014329.3610326-1-mawupeng1@huawei.com> (raw)
From: Ma Wupeng <mawupeng1@huawei.com>
Fix two bugs during migrate folio if folio is poisoned.
Changelog since v2:
- re-order patches
- fix compile errors
- modify patch #2 as suggested
Changelog since v1:
- update ttu flag inside unmap_poisoned_folio.
- check folio ref count before unmap HWpoisoned folio.
Ma Wupeng (3):
mm: memory-failure: update ttu flag inside unmap_poisoned_folio
mm: memory-hotplug: check folio ref count first in do_migrate_range
hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio
mm/internal.h | 5 ++--
mm/memory-failure.c | 61 +++++++++++++++++++++++----------------------
mm/memory_hotplug.c | 26 +++++++++----------
3 files changed, 46 insertions(+), 46 deletions(-)
--
2.43.0
next reply other threads:[~2025-02-17 1:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 1:43 Wupeng Ma [this message]
2025-02-17 1:43 ` [PATCH v3 1/3] mm: memory-failure: update ttu flag inside unmap_poisoned_folio Wupeng Ma
2025-02-19 2:50 ` Miaohe Lin
2025-02-19 3:34 ` mawupeng
2025-02-19 6:06 ` [PATCH v3] " Wupeng Ma
2025-02-19 23:41 ` Andrew Morton
2025-03-19 17:21 ` Arthur Marsh
2025-03-20 2:40 ` mawupeng
2025-02-17 1:43 ` [PATCH v3 2/3] mm: memory-hotplug: check folio ref count first in do_migrate_range Wupeng Ma
2025-02-17 9:30 ` David Hildenbrand
2025-02-19 3:15 ` Miaohe Lin
2025-02-17 1:43 ` [PATCH v3 3/3] hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Wupeng Ma
2025-02-19 3:17 ` Miaohe Lin
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=20250217014329.3610326-1-mawupeng1@huawei.com \
--to=mawupeng1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
/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