From: Mike Rapoport <rppt@kernel.org>
To: Qi Zheng <arch0.zheng@gmail.com>
Cc: Michal Hocko <mhocko@suse.com>,
David Hildenbrand <david@redhat.com>,
Qi Zheng <zhengqi.arch@bytedance.com>,
Vlastimil Babka <vbabka@suse.cz>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Teng Hu <huteng.ht@bytedance.com>,
Matthew Wilcox <willy@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
Oscar Salvador <osalvador@suse.de>,
Muchun Song <muchun.song@linux.dev>,
x86@kernel.org
Subject: Re: [PATCH] mm: page_alloc: don't allocate page from memoryless nodes
Date: Tue, 17 Oct 2023 09:12:10 +0300 [thread overview]
Message-ID: <20231017061210.GW3303@kernel.org> (raw)
In-Reply-To: <8f506561-44f7-a243-f0cc-59543f487e4d@gmail.com>
On Mon, Oct 16, 2023 at 12:09:42PM +0800, Qi Zheng wrote:
> Hi Mike,
>
> On 2023/2/15 17:30, Mike Rapoport wrote:
> [...]
> >
> > How about we try this:
> >
> > From b670120bcacd3fe34a40d7179c70ca2ab69279e0 Mon Sep 17 00:00:00 2001
> > From: "Mike Rapoport (IBM)" <rppt@kernel.org>
> > Date: Wed, 15 Feb 2023 11:12:18 +0200
> > Subject: [PATCH] x86/mm: drop 4MB restriction on minimal NUMA node size
> >
> > Qi Zheng reports crashes in a production environment and provides a
> > simplified example as a reproducer:
> >
> > For example, if we use qemu to start a two NUMA node kernel,
> > one of the nodes has 2M memory (less than NODE_MIN_SIZE),
> > and the other node has 2G, then we will encounter the
> > following panic:
> >
> > [ 0.149844] BUG: kernel NULL pointer dereference, address: 0000000000000000
> > [ 0.150783] #PF: supervisor write access in kernel mode
> > [ 0.151488] #PF: error_code(0x0002) - not-present page
> > <...>
> > [ 0.156056] RIP: 0010:_raw_spin_lock_irqsave+0x22/0x40
> > <...>
> > [ 0.169781] Call Trace:
> > [ 0.170159] <TASK>
> > [ 0.170448] deactivate_slab+0x187/0x3c0
> > [ 0.171031] ? bootstrap+0x1b/0x10e
> > [ 0.171559] ? preempt_count_sub+0x9/0xa0
> > [ 0.172145] ? kmem_cache_alloc+0x12c/0x440
> > [ 0.172735] ? bootstrap+0x1b/0x10e
> > [ 0.173236] bootstrap+0x6b/0x10e
> > [ 0.173720] kmem_cache_init+0x10a/0x188
> > [ 0.174240] start_kernel+0x415/0x6ac
> > [ 0.174738] secondary_startup_64_no_verify+0xe0/0xeb
> > [ 0.175417] </TASK>
> > [ 0.175713] Modules linked in:
> > [ 0.176117] CR2: 0000000000000000
> >
> > The crashes happen because of inconsistency between nodemask that has
> > nodes with less than 4MB as memoryless and the actual memory fed into
> > core mm.
> >
> > The commit 9391a3f9c7f1 ("[PATCH] x86_64: Clear more state when ignoring
> > empty node in SRAT parsing") that introduced minimal size of a NUMA node
> > does not explain why a node size cannot be less than 4MB and what boot
> > failures this restriction might fix.
> >
> > Since then a lot has changed and core mm won't confuse badly about small
> > node sizes.
> >
> > Drop the limitation for the minimal node size.
> >
> > Link: https://lore.kernel.org/all/20230212110305.93670-1-zhengqi.arch@bytedance.com/
> > Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
> > ---
> > arch/x86/include/asm/numa.h | 7 -------
> > arch/x86/mm/numa.c | 7 -------
> > 2 files changed, 14 deletions(-)
>
> What's the current progress on this patch? This patch doesn't seem to be
> merged into any trees. Did I miss something?
Looks like it fell between the cracks. I'll resend.
> Thanks,
> Qi
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-10-17 6:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 11:03 [PATCH] mm: page_alloc: don't allocate page from memoryless nodes Qi Zheng
2023-02-13 8:47 ` Vlastimil Babka
2023-02-13 11:00 ` Qi Zheng
2023-02-14 8:42 ` Vlastimil Babka
2023-02-14 9:17 ` David Hildenbrand
2023-02-14 9:43 ` Mike Rapoport
2023-02-14 10:26 ` Qi Zheng
2023-02-14 11:22 ` David Hildenbrand
2023-02-14 11:26 ` Qi Zheng
2023-02-14 11:29 ` David Hildenbrand
2023-02-14 11:38 ` Qi Zheng
2023-02-14 11:44 ` Mike Rapoport
2023-02-14 11:48 ` David Hildenbrand
2023-02-14 11:58 ` David Hildenbrand
2023-02-14 12:09 ` [External] " Qi Zheng
2023-02-14 13:38 ` Michal Hocko
2023-02-15 9:30 ` Mike Rapoport
2023-02-15 9:41 ` Qi Zheng
2023-02-15 10:08 ` Mike Rapoport
2023-02-15 10:19 ` Qi Zheng
2023-02-15 9:43 ` David Hildenbrand
2023-02-15 10:04 ` Mike Rapoport
2023-02-15 10:11 ` David Hildenbrand
2023-02-15 16:55 ` Michal Hocko
2023-10-16 4:09 ` Qi Zheng
2023-10-17 6:12 ` Mike Rapoport [this message]
2023-02-14 12:33 ` Qi Zheng
2023-02-14 12:46 ` Mike Rapoport
2023-02-14 10:13 ` Qi Zheng
2023-02-14 9:10 ` Mike Rapoport
2023-02-14 10:33 ` Qi Zheng
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=20231017061210.GW3303@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arch0.zheng@gmail.com \
--cc=david@redhat.com \
--cc=huteng.ht@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=zhengqi.arch@bytedance.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 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.