From: Mike Rapoport <rppt@linux.ibm.com> To: Qian Cai <quic_qiancai@quicinc.com>, Andrew Morton <akpm@linux-foundation.org> Cc: Mark Rutland <mark.rutland@arm.com>, Naresh Kamboju <naresh.kamboju@linaro.org>, Miles Chen <miles.chen@mediatek.com>, Linux-Next Mailing List <linux-next@vger.kernel.org>, linux-mm <linux-mm@kvack.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, open list <linux-kernel@vger.kernel.org>, Will Deacon <will@kernel.org>, lkft-triage@lists.linaro.org, regressions@lists.linux.dev, Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Christophe Leroy <christophe.leroy@csgroup.eu> Subject: Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c Date: Tue, 15 Jun 2021 22:21:32 +0300 [thread overview] Message-ID: <YMj9vHhHOiCVN4BF@linux.ibm.com> (raw) In-Reply-To: <076665b9-9fb1-71da-5f7d-4d2c7f892103@quicinc.com> On Tue, Jun 15, 2021 at 10:50:31AM -0400, Qian Cai wrote: > > > On 6/15/2021 9:19 AM, Mark Rutland wrote: > > Looking some more, it looks like that's correct in isolation, but it > > clashes with commit: > > > > 5831eedad2ac6f38 ("mm: replace CONFIG_NEED_MULTIPLE_NODES with CONFIG_NUMA") > > Just a data point. Reverting the commit alone fixed the same crash for me. Yeah, that commit didn't take into the account the change in pgdat_to_phys(). The patch below should fix it. In the long run I think we should get rid of contig_page_data and allocate NODE_DATA(0) for !NUMA case as well. Andrew, can you please add this as a fixup to "mm: replace CONFIG_NEED_MULTIPLE_NODES with CONFIG_NUMA"? diff --git a/mm/sparse.c b/mm/sparse.c index a0e9cdb5bc38..6326cdf36c4f 100644 --- a/mm/sparse.c +++ b/mm/sparse.c @@ -347,7 +347,7 @@ size_t mem_section_usage_size(void) static inline phys_addr_t pgdat_to_phys(struct pglist_data *pgdat) { -#ifndef CONFIG_NEED_MULTIPLE_NODES +#ifndef CONFIG_NUMA return __pa_symbol(pgdat); #else return __pa(pgdat); -- Sincerely yours, Mike.
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@linux.ibm.com> To: Qian Cai <quic_qiancai@quicinc.com>, Andrew Morton <akpm@linux-foundation.org> Cc: Mark Rutland <mark.rutland@arm.com>, Naresh Kamboju <naresh.kamboju@linaro.org>, Miles Chen <miles.chen@mediatek.com>, Linux-Next Mailing List <linux-next@vger.kernel.org>, linux-mm <linux-mm@kvack.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, open list <linux-kernel@vger.kernel.org>, Will Deacon <will@kernel.org>, lkft-triage@lists.linaro.org, regressions@lists.linux.dev, Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Christophe Leroy <christophe.leroy@csgroup.eu> Subject: Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c Date: Tue, 15 Jun 2021 22:21:32 +0300 [thread overview] Message-ID: <YMj9vHhHOiCVN4BF@linux.ibm.com> (raw) In-Reply-To: <076665b9-9fb1-71da-5f7d-4d2c7f892103@quicinc.com> On Tue, Jun 15, 2021 at 10:50:31AM -0400, Qian Cai wrote: > > > On 6/15/2021 9:19 AM, Mark Rutland wrote: > > Looking some more, it looks like that's correct in isolation, but it > > clashes with commit: > > > > 5831eedad2ac6f38 ("mm: replace CONFIG_NEED_MULTIPLE_NODES with CONFIG_NUMA") > > Just a data point. Reverting the commit alone fixed the same crash for me. Yeah, that commit didn't take into the account the change in pgdat_to_phys(). The patch below should fix it. In the long run I think we should get rid of contig_page_data and allocate NODE_DATA(0) for !NUMA case as well. Andrew, can you please add this as a fixup to "mm: replace CONFIG_NEED_MULTIPLE_NODES with CONFIG_NUMA"? diff --git a/mm/sparse.c b/mm/sparse.c index a0e9cdb5bc38..6326cdf36c4f 100644 --- a/mm/sparse.c +++ b/mm/sparse.c @@ -347,7 +347,7 @@ size_t mem_section_usage_size(void) static inline phys_addr_t pgdat_to_phys(struct pglist_data *pgdat) { -#ifndef CONFIG_NEED_MULTIPLE_NODES +#ifndef CONFIG_NUMA return __pa_symbol(pgdat); #else return __pa(pgdat); -- Sincerely yours, Mike. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-15 19:22 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-15 11:11 [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c Naresh Kamboju 2021-06-15 11:11 ` Naresh Kamboju 2021-06-15 11:50 ` Will Deacon 2021-06-15 11:50 ` Will Deacon 2021-06-17 12:15 ` Naresh Kamboju 2021-06-17 12:15 ` Naresh Kamboju 2021-06-15 12:47 ` Mark Rutland 2021-06-15 12:47 ` Mark Rutland 2021-06-15 13:19 ` Mark Rutland 2021-06-15 13:19 ` Mark Rutland 2021-06-15 14:50 ` Qian Cai 2021-06-15 14:50 ` Qian Cai 2021-06-15 19:21 ` Mike Rapoport [this message] 2021-06-15 19:21 ` Mike Rapoport 2021-06-15 23:34 ` Stephen Rothwell 2021-06-15 23:34 ` Stephen Rothwell 2021-06-15 23:40 ` Miles Chen 2021-06-15 23:40 ` Miles Chen 2021-06-16 0:29 ` Miles Chen 2021-06-16 0:29 ` Miles Chen
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=YMj9vHhHOiCVN4BF@linux.ibm.com \ --to=rppt@linux.ibm.com \ --cc=akpm@linux-foundation.org \ --cc=ardb@kernel.org \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=christophe.leroy@csgroup.eu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-next@vger.kernel.org \ --cc=lkft-triage@lists.linaro.org \ --cc=mark.rutland@arm.com \ --cc=miles.chen@mediatek.com \ --cc=naresh.kamboju@linaro.org \ --cc=quic_qiancai@quicinc.com \ --cc=regressions@lists.linux.dev \ --cc=sfr@canb.auug.org.au \ --cc=will@kernel.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: linkBe 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.