From: Wei Yang <richard.weiyang@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org,
Marek Marczykowski-G??recki <marmarek@invisiblethingslab.com>,
Michal Hocko <mhocko@kernel.org>,
Wei Yang <richard.weiyang@gmail.com>
Subject: Re: [PATCH] mm, page_alloc: fix build_zonerefs_node()
Date: Fri, 8 Apr 2022 23:21:29 +0000 [thread overview]
Message-ID: <20220408232129.caboqxtw6s4nmgde@master> (raw)
In-Reply-To: <1028ca3c-5b6c-d95e-9372-ae64b1fcbc82@redhat.com>
On Thu, Apr 07, 2022 at 11:46:13AM +0200, David Hildenbrand wrote:
>On 07.04.22 11:32, Juergen Gross wrote:
>> Since commit 9d3be21bf9c0 ("mm, page_alloc: simplify zonelist
>> initialization") only zones with free memory are included in a built
>> zonelist. This is problematic when e.g. all memory of a zone has been
>> ballooned out.
>>
>> Use populated_zone() when building a zonelist as it has been done
>> before that commit.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: 9d3be21bf9c0 ("mm, page_alloc: simplify zonelist initialization")
>> Reported-by: Marek Marczykowski-G??recki <marmarek@invisiblethingslab.com>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>> mm/page_alloc.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> index bdc8f60ae462..3d0662af3289 100644
>> --- a/mm/page_alloc.c
>> +++ b/mm/page_alloc.c
>> @@ -6128,7 +6128,7 @@ static int build_zonerefs_node(pg_data_t *pgdat, struct zoneref *zonerefs)
>> do {
>> zone_type--;
>> zone = pgdat->node_zones + zone_type;
>> - if (managed_zone(zone)) {
>> + if (populated_zone(zone)) {
>> zoneref_set_zone(zone, &zonerefs[nr_zones++]);
>> check_highest_zone(zone_type);
>> }
>
>Let's see if we have to find another way to properly handle fadump.
>
>Acked-by: David Hildenbrand <david@redhat.com>
Ok, I see the point.
Reviewed-by: Wei Yang <richard.weiyang@gmail.com>
>
>--
>Thanks,
>
>David / dhildenb
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2022-04-08 23:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 9:32 [PATCH] mm, page_alloc: fix build_zonerefs_node() Juergen Gross
2022-04-07 9:46 ` David Hildenbrand
2022-04-07 10:06 ` Juergen Gross
2022-04-08 23:21 ` Wei Yang [this message]
2022-04-07 10:34 ` Michal Hocko
2022-04-07 10:45 ` Juergen Gross
2022-04-07 11:07 ` Michal Hocko
2022-04-07 11:17 ` Juergen Gross
2022-04-07 11:40 ` Michal Hocko
2022-04-07 11:48 ` Michal Hocko
2022-04-07 11:58 ` David Hildenbrand
2022-04-07 12:04 ` Michal Hocko
2022-04-07 12:12 ` David Hildenbrand
2022-04-07 13:23 ` Michal Hocko
2022-04-07 12:32 ` Mel Gorman
2022-04-07 12:49 ` Juergen Gross
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=20220408232129.caboqxtw6s4nmgde@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marmarek@invisiblethingslab.com \
--cc=mhocko@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.