From: Zi Yan <ziy@nvidia.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Regressions <regressions@lists.linux.dev>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Andrew Morton <akpm@linux-foundation.org>,
doru iorgulescu <doru.iorgulescu1@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Fabiano Rosas <farosas@linux.ibm.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Disha Goel <disgoel@linux.vnet.ibm.com>
Subject: Re: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
Date: Wed, 24 May 2023 07:48:21 -0400 [thread overview]
Message-ID: <D0217FEF-6E59-4458-BC34-A5FDB3097176@nvidia.com> (raw)
In-Reply-To: <2a1cd5e6-01f7-66f9-1f9d-c655cc3f919b@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
On 24 May 2023, at 6:58, Bagas Sanjaya wrote:
> Hi,
>
> I notice a powerpc[64?] build regression on Bugzilla [1]. Quoting from it:
>
>> CC arch/powerpc/kernel/asm-offsets.s
>> In file included from ./include/linux/gfp.h:7,
>> from ./include/linux/xarray.h:15,
>> from ./include/linux/list_lru.h:14,
>> from ./include/linux/fs.h:13,
>> from ./include/linux/compat.h:17,
>> from arch/powerpc/kernel/asm-offsets.c:12:
>> ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE
>> 1735 | #error Allocator MAX_ORDER exceeds SECTION_SIZE
>> | ^~~~~
>> make[5]: *** [scripts/Makefile.build:114: arch/powerpc/kernel/asm-offsets.s] Error 1
By checking the config file from the bugzilla, ARCH_FORCE_MAX_ORDER is set to 9,
(SECTION_SIZE is 24 and 64KB page is used, so 9+16=25>24) but it should be 8
after recent MAX_ORDER changes. I guess the user was using an old config file.
Changing ARCH_FORCE_MAX_ORDER to 8 in the config should fix the issue.
>
> Apparently removing the errored line solves the problem for the reporter
> (the attached dmesg on [2] looks fine at a glance).
>
> Anyway, I'm adding it to regzbot:
>
> #regzbot introduced: 23baf831a32c04f https://bugzilla.kernel.org/show_bug.cgi?id=217477
> #regzbot title: Allocator MAX_ORDER exceeds SECTION_SIZE caused by MAX_ORDER redefinition
>
> Thanks.
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217477
> [2]: https://bugzilla.kernel.org/show_bug.cgi?id=217477#c1
>
> --
> An old man doll... just what I always wanted! - Clara
--
Best Regards,
Yan, Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2023-05-24 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 10:58 Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression) Bagas Sanjaya
2023-05-24 11:48 ` Zi Yan [this message]
2023-05-24 12:58 ` Bagas Sanjaya
[not found] ` <CA+39qUjOA53UO4oYOzrUJqdYq8A3hbnnxpSV8nfqh0T5KiNL9A@mail.gmail.com>
2023-05-24 13:39 ` Bagas Sanjaya
2023-05-24 15:03 ` Michael Ellerman
2023-05-25 0:57 ` Bagas Sanjaya
[not found] ` <CA+39qUjP48n=EwqHzwdGkBE8SC-nTNZHZxEfG4r4hWC-5Bg4HA@mail.gmail.com>
2023-05-29 8:24 ` Bagas Sanjaya
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=D0217FEF-6E59-4458-BC34-A5FDB3097176@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=bagasdotme@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=disgoel@linux.vnet.ibm.com \
--cc=doru.iorgulescu1@gmail.com \
--cc=farosas@linux.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=regressions@lists.linux.dev \
/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).