From: David Hildenbrand <david@redhat.com>
To: Mike Rapoport <rppt@linux.ibm.com>, David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH] mm, page_alloc: check pfn is valid before moving to freelist
Date: Thu, 14 Apr 2022 16:02:32 +0200 [thread overview]
Message-ID: <91b35970-b68e-580f-b17d-789fcc2e1c47@redhat.com> (raw)
In-Reply-To: <Ylc437iBoQ4AU6zT@linux.ibm.com>
On 13.04.22 22:55, Mike Rapoport wrote:
> On Tue, Apr 12, 2022 at 02:05:51PM -0700, David Rientjes wrote:
>> On Tue, 12 Apr 2022, Andrew Morton wrote:
>>
>>> On Tue, 12 Apr 2022 13:16:23 -0700 Sudarshan Rajagopalan <quic_sudaraja@quicinc.com> wrote:
>>>
>>>> Check if pfn is valid before or not before moving it to freelist.
>>>>
>>>> There are possible scenario where a pageblock can have partial physical
>>>> hole and partial part of System RAM. This happens when base address in RAM
>>>> partition table is not aligned to pageblock size.
>>>>
>>>> ...
>>>>
>>>>
>>>> Signed-off-by: Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>
>>>> Fixes: 4c7b9896621be ("mm: remove pfn_valid_within() and CONFIG_HOLES_IN_ZONE")
>>>
>>> I made that 859a85ddf90e714092dea71a0e54c7b9896621be and added
>>> cc:stable. I'll await reviewer input before proceeding further.
>>>
>>
>> Acked-by: David Rientjes <rientjes@google.com>
>>
>>>> --- a/mm/page_alloc.c
>>>> +++ b/mm/page_alloc.c
>>>> @@ -2521,6 +2521,11 @@ static int move_freepages(struct zone *zone,
>>>> int pages_moved = 0;
>>>>
>>>> for (pfn = start_pfn; pfn <= end_pfn;) {
>>>> + if (!pfn_valid(pfn)) {
>>>
>>> Readers will wonder how we can encounter an invalid pfn here. A small
>>> comment might help clue them in.
>>>
>>
>> Sudarshan can correct me if I'm wrong, but this has to do with the
>> pageblock alignment of the caller that assumes all pages in the range has
>> an underlying struct page that we can access but that fails to hold true
>> when we have a memory hole. A comment would definitely help:
>
> We do have a struct page for every page in a pageblock even if there is a
> hole in the physical memory. If this is not the case, there is more
> fundamental bug that should be fixed.
Also, I dislike handling such a corner case in a way that affects all
other sane cases. move_freepages() is also used for page isolation.
I agree that this should be fixed differently, if possible.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-04-14 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 20:16 [PATCH] mm, page_alloc: check pfn is valid before moving to freelist Sudarshan Rajagopalan
2022-04-12 20:16 ` Sudarshan Rajagopalan
2022-04-12 20:59 ` Andrew Morton
2022-04-12 21:05 ` David Rientjes
2022-04-13 20:55 ` Mike Rapoport
2022-04-14 14:02 ` David Hildenbrand [this message]
2022-04-13 20:48 ` Mike Rapoport
2022-04-14 21:00 ` Sudarshan Rajagopalan
2022-04-18 7:24 ` Mike Rapoport
2022-04-18 22:32 ` Sudarshan Rajagopalan
2022-04-19 6:45 ` Mike Rapoport
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=91b35970-b68e-580f-b17d-789fcc2e1c47@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=quic_sudaraja@quicinc.com \
--cc=rientjes@google.com \
--cc=rppt@linux.ibm.com \
--cc=surenb@google.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;
as well as URLs for NNTP newsgroup(s).