From: Jane Chu <jane.chu@oracle.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH v4 4/6] mm: migrate: support poisoned recover from migrate folio
Date: Thu, 6 Jun 2024 15:31:28 -0700 [thread overview]
Message-ID: <f0aa30f6-073f-4cbf-9046-136dd9ad3336@oracle.com> (raw)
In-Reply-To: <0290a474-39f4-4549-9fc8-06ccd6321d5d@oracle.com>
On 6/6/2024 3:28 PM, Jane Chu wrote:
> On 6/6/2024 2:27 PM, Jane Chu wrote:
>
>> On 6/3/2024 2:24 AM, Kefeng Wang wrote:
>>> diff --git a/mm/migrate.c b/mm/migrate.c
>>> index e930376c261a..28aa9da95781 100644
>>> --- a/mm/migrate.c
>>> +++ b/mm/migrate.c
>>> @@ -663,16 +663,29 @@ static int __migrate_folio(struct
>>> address_space *mapping, struct folio *dst,
>>> struct folio *src, void *src_private,
>>> enum migrate_mode mode)
>>> {
>>> - int rc;
>>> + int ret, expected_cnt = folio_expected_refs(mapping, src);
>>> - rc = folio_migrate_mapping(mapping, dst, src, 0);
>>> - if (rc != MIGRATEPAGE_SUCCESS)
>>> - return rc;
>>> + if (!mapping) {
>>> + if (folio_ref_count(src) != expected_cnt)
>>> + return -EAGAIN;
>>> + } else {
>>> + if (!folio_ref_freeze(src, expected_cnt))
>>> + return -EAGAIN;
>>> + }
>>> +
>>
>> Let me take a guess, the reason you split up folio_migrate_copy() is
>> that
>>
>> folio_mc_copy() should be done before the 'src' folio's ->flags is
>> changed, right?
>>
>> Is there any other reason? Could you add a comment please?
>
> I see, both the clearing of the 'dirty' bit in the source folio, and
> the xas_store of the
>
> new folio to the mapping, these need to be done after folio_mc_copy
> considering in the
>
> event of UE, memory_failure() is called to handle the poison in the
> source page.
>
> That said, since the poisoned page was queued up and handling is
> asynchronous, so in
>
> theory, there is an extremely unlikely chance that memory_failure() is
> invoked after
>
> folio_migrate_mapping(), do you think things would still be cool?
Hmm, perhaps after xas_store, the source folio->mapping should be set to
NULL.
thanks,
-jane
>
>
> thanks,
>
> -jane
>
>>
>>> + ret = folio_mc_copy(dst, src);
>>> + if (unlikely(ret)) {
>>> + if (mapping)
>>> + folio_ref_unfreeze(src, expected_cnt);
>>> + return ret;
>>> + }
>>> +
>>> + __folio_migrate_mapping(mapping, dst, src, expected_cnt);
>>> if (src_private)
>>> folio_attach_private(dst, folio_detach_private(src));
>>> - folio_migrate_copy(dst, src);
>>> + folio_migrate_flags(dst, src);
>>> return MIGRATEPAGE_SUCCESS;
>>> }
>>
>> thanks,
>>
>> -jane
>>
>>
>
next prev parent reply other threads:[~2024-06-06 22: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 " 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 [this message]
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
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=f0aa30f6-073f-4cbf-9046-136dd9ad3336@oracle.com \
--to=jane.chu@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=wangkefeng.wang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox