From: Miaohe Lin <linmiaohe@huawei.com>
To: Wupeng Ma <mawupeng1@huawei.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<akpm@linux-foundation.org>, <david@redhat.com>,
<osalvador@suse.de>, <nao.horiguchi@gmail.com>, <mhocko@suse.com>
Subject: Re: [PATCH v2 3/3] mm: memory-hotplug: check folio ref count first in do_migrate_rang
Date: Mon, 20 Jan 2025 14:32:20 +0800 [thread overview]
Message-ID: <3b993af4-1fe2-b250-5d07-5840f1ad530d@huawei.com> (raw)
In-Reply-To: <20250116061657.227027-4-mawupeng1@huawei.com>
On 2025/1/16 14:16, Wupeng Ma wrote:
> From: Ma Wupeng <mawupeng1@huawei.com>
>
> If a folio has an increased reference count, folio_try_get() will acquire
> it, perform necessary operations, and then release it. In the case of a
> poisoned folio without an elevated reference count (which is unlikely for
> memory-failure), folio_try_get() will simply bypass it.
>
> Therefore, relocate the folio_try_get() function, responsible for checking
> and acquiring this reference count at first.
>
> Signed-off-by: Ma Wupeng <mawupeng1@huawei.com>
> ---
> mm/memory_hotplug.c | 14 ++++----------
> 1 file changed, 4 insertions(+), 10 deletions(-)
>
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 2815bd4ea483..3fb75ee185c6 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -1786,6 +1786,9 @@ static void do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
> page = pfn_to_page(pfn);
> folio = page_folio(page);
>
> + if (!folio_try_get(folio))
> + continue;
> +
> /*
> * No reference or lock is held on the folio, so it might
> * be modified concurrently (e.g. split). As such,
> @@ -1795,12 +1798,6 @@ static void do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
> if (folio_test_large(folio))
> pfn = folio_pfn(folio) + folio_nr_pages(folio) - 1;
>
> - /*
> - * HWPoison pages have elevated reference counts so the migration would
> - * fail on them. It also doesn't make any sense to migrate them in the
> - * first place. Still try to unmap such a page in case it is still mapped
> - * (keep the unmap as the catch all safety net).
> - */
> if (folio_test_hwpoison(folio) ||
> (folio_test_large(folio) && folio_test_has_hwpoisoned(folio))) {
> if (WARN_ON(folio_test_lru(folio)))
> @@ -1811,12 +1808,9 @@ static void do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
> folio_unlock(folio);
> }
>
> - continue;
> + goto put_folio;
> }
>
> - if (!folio_try_get(folio))
> - continue;
> -
> if (unlikely(page_folio(page) != folio))
> goto put_folio;
Will it be necessary to move this check above folio_test_hwpoison trunk too?
Thanks.
.
next prev parent reply other threads:[~2025-01-20 6:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 6:16 [PATCH v2 0/3] mm: memory_failure: unmap poisoned filio during migrate properly Wupeng Ma
2025-01-16 6:16 ` [PATCH v2 1/3] mm: memory-failure: update ttu flag inside unmap_poisoned_folio Wupeng Ma
2025-01-17 3:57 ` kernel test robot
2025-01-17 4:16 ` mawupeng
2025-01-17 4:39 ` kernel test robot
2025-01-17 4:49 ` kernel test robot
2025-01-20 6:24 ` Miaohe Lin
2025-01-20 7:49 ` David Hildenbrand
2025-01-20 8:46 ` David Hildenbrand
2025-01-21 3:20 ` Miaohe Lin
2025-01-21 7:58 ` David Hildenbrand
2025-01-22 7:38 ` Miaohe Lin
2025-01-21 2:46 ` Miaohe Lin
2025-01-20 9:06 ` mawupeng
2025-01-20 7:55 ` David Hildenbrand
2025-01-16 6:16 ` [PATCH v2 2/3] hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Wupeng Ma
2025-01-20 9:25 ` David Hildenbrand
2025-01-16 6:16 ` [PATCH v2 3/3] mm: memory-hotplug: check folio ref count first in do_migrate_rang Wupeng Ma
2025-01-20 6:32 ` Miaohe Lin [this message]
2025-01-21 2:17 ` mawupeng
2025-01-20 8:01 ` David Hildenbrand
2025-01-20 9:11 ` mawupeng
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=3b993af4-1fe2-b250-5d07-5840f1ad530d@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawupeng1@huawei.com \
--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