Re: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)

Zi Yan
2023-05-24T11:48:31Z

[-- 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 --]