From: Jane Chu <jane.chu@oracle.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
akpm@linux-foundation.org, linux-mm@kvack.org
Cc: 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>,
Oscar Salvador <osalvador@suse.de>,
Lance Yang <ioworker0@gmail.com>
Subject: Re: [PATCH v4 5/6] fs: hugetlbfs: support poison recover from hugetlbfs_migrate_folio()
Date: Thu, 6 Jun 2024 16:30:41 -0700 [thread overview]
Message-ID: <f1cbad32-7125-446e-b3df-b0380d5dedd4@oracle.com> (raw)
In-Reply-To: <20240603092439.3360652-6-wangkefeng.wang@huawei.com>
On 6/3/2024 2:24 AM, Kefeng Wang wrote:
> This is similar to __migrate_folio(), use folio_mc_copy() in HugeTLB
> folio migration to avoid panic when copy from poisoned folio.
>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> fs/hugetlbfs/inode.c | 2 +-
> mm/migrate.c | 14 +++++++++-----
> 2 files changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> index 6df794ed4066..1107e5aa8343 100644
> --- a/fs/hugetlbfs/inode.c
> +++ b/fs/hugetlbfs/inode.c
> @@ -1128,7 +1128,7 @@ static int hugetlbfs_migrate_folio(struct address_space *mapping,
> hugetlb_set_folio_subpool(src, NULL);
> }
>
> - folio_migrate_copy(dst, src);
> + folio_migrate_flags(dst, src);
>
> return MIGRATEPAGE_SUCCESS;
> }
> diff --git a/mm/migrate.c b/mm/migrate.c
> index 28aa9da95781..e9b52a86f539 100644
> --- a/mm/migrate.c
> +++ b/mm/migrate.c
> @@ -532,15 +532,19 @@ int migrate_huge_page_move_mapping(struct address_space *mapping,
> struct folio *dst, struct folio *src)
> {
> XA_STATE(xas, &mapping->i_pages, folio_index(src));
> - int expected_count;
> + int ret, expected_count = folio_expected_refs(mapping, src);
>
> - xas_lock_irq(&xas);
> - expected_count = folio_expected_refs(mapping, src);
> - if (!folio_ref_freeze(src, expected_count)) {
> - xas_unlock_irq(&xas);
> + if (!folio_ref_freeze(src, expected_count))
> return -EAGAIN;
> +
> + ret = folio_mc_copy(dst, src);
> + if (unlikely(ret)) {
> + folio_ref_unfreeze(src, expected_count);
> + return ret;
> }
>
> + xas_lock_irq(&xas);
> +
> dst->index = src->index;
> dst->mapping = src->mapping;
>
Look good!
Reviewed-by: Jane Chu <jane.chu@oracle.com>
-jane
next prev parent reply other threads:[~2024-06-06 23:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 9:24 [PATCH v4 0/6] mm: migrate: support poison recover from migrate folio Kefeng Wang
2024-06-03 9:24 ` [PATCH v4 1/6] mm: move memory_failure_queue() into copy_mc_[user]_highpage() Kefeng Wang
2024-06-04 19:38 ` Jane Chu
2024-06-06 2:28 ` Miaohe Lin
2024-06-03 9:24 ` [PATCH v4 2/6] mm: add folio_mc_copy() Kefeng Wang
2024-06-04 19:41 ` Jane Chu
2024-06-05 3:31 ` Andrew Morton
2024-06-05 7:15 ` Kefeng Wang
2024-06-06 2:36 ` Miaohe Lin
2024-06-03 9:24 ` [PATCH v4 3/6] mm: migrate: split folio_migrate_mapping() Kefeng Wang
2024-06-06 0:54 ` Jane Chu
2024-06-06 1:24 ` Kefeng Wang
2024-06-06 1:55 ` Matthew Wilcox
2024-06-06 2:24 ` Kefeng Wang
2024-06-06 18:28 ` Jane Chu
2024-06-03 9:24 ` [PATCH v4 4/6] mm: migrate: support poisoned recover from migrate folio Kefeng Wang
2024-06-06 21:27 ` Jane Chu
2024-06-06 22:28 ` Jane Chu
2024-06-06 22:31 ` Jane Chu
2024-06-07 4:01 ` Kefeng Wang
2024-06-07 15:59 ` Jane Chu
2024-06-03 9:24 ` [PATCH v4 5/6] fs: hugetlbfs: support poison recover from hugetlbfs_migrate_folio() Kefeng Wang
2024-06-06 23:30 ` Jane Chu [this message]
2024-06-03 9:24 ` [PATCH v4 6/6] mm: migrate: remove folio_migrate_copy() Kefeng Wang
2024-06-06 23:46 ` Jane Chu
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=f1cbad32-7125-446e-b3df-b0380d5dedd4@oracle.com \
--to=jane.chu@oracle.com \
--cc=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=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