linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: David Hildenbrand <david@redhat.com>, <akpm@linux-foundation.org>
Cc: <mhocko@suse.com>, <vbabka@suse.cz>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/page_isolation: fix potential missing call to unset_migratetype_isolate()
Date: Mon, 6 Sep 2021 17:38:58 +0800	[thread overview]
Message-ID: <ebbef13c-921e-c385-1233-a7aeecec6127@huawei.com> (raw)
In-Reply-To: <dcfcacf2-0018-3b91-6da5-2420bad889c1@redhat.com>

On 2021/9/6 17:27, David Hildenbrand wrote:
> On 04.09.21 11:20, Miaohe Lin wrote:
>> In start_isolate_page_range() undo path, pfn_to_online_page() just checks
>> the first pfn in a pageblock while __first_valid_page() will traverse the
>> pageblock until the first online pfn is found. So we may miss the call to
>> unset_migratetype_isolate() in undo path and pages will remain isolated
>> unexpectedly. Fix this by calling undo_isolate_page_range() and this will
>> also help to remove some duplicated codes.
>>
>> Fixes: 2ce13640b3f4 ("mm: __first_valid_page skip over offline pages")
> 
> While that is true, we shouldn't ever trigger, neither via cma, virtio-mem nor memory offlining, because essentially all operate on MAX_ORDER -1 -aligned ranges without memory holes.

I think this should never trigger too. It's a theoretical issue. So is the Fixes tag necessary ?

> 
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>>   mm/page_isolation.c | 9 +--------
>>   1 file changed, 1 insertion(+), 8 deletions(-)
>>
>> diff --git a/mm/page_isolation.c b/mm/page_isolation.c
>> index 471e3a13b541..9bb562d5d194 100644
>> --- a/mm/page_isolation.c
>> +++ b/mm/page_isolation.c
>> @@ -202,14 +202,7 @@ int start_isolate_page_range(unsigned long start_pfn, unsigned long end_pfn,
>>       }
>>       return 0;
>>   undo:
>> -    for (pfn = start_pfn;
>> -         pfn < undo_pfn;
>> -         pfn += pageblock_nr_pages) {
>> -        struct page *page = pfn_to_online_page(pfn);
>> -        if (!page)
>> -            continue;
>> -        unset_migratetype_isolate(page, migratetype);
>> -    }
>> +    undo_isolate_page_range(start_pfn, undo_pfn, migratetype);
>>   
> 
> It'd be even cleaner to drop the label completely and call it from the single callsite. We can even avoid undo_pfn ...
> 
> if (page && set_migratetype_isolate(page, migratetype, flags)) {
>     undo_isolate_page_range(start_pfn, pfn, migratetype);
>     return -EBUSY;
> }
> 

Looks much better. Will do it later. Many thanks. :)

> If pfn == start_pfn, undo_isolate_page_range() will simply do nothing.
> 
>>       return -EBUSY;
>>   }
>>
> 


  reply	other threads:[~2021-09-06  9:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04  9:20 [PATCH] mm/page_isolation: fix potential missing call to unset_migratetype_isolate() Miaohe Lin
2021-09-06  9:27 ` David Hildenbrand
2021-09-06  9:38   ` Miaohe Lin [this message]
2021-09-06  9:46     ` David Hildenbrand
2021-09-06 11:42       ` 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=ebbef13c-921e-c385-1233-a7aeecec6127@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=mhocko@suse.com \
    --cc=vbabka@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).