linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
@ 2023-05-24 10:58 Bagas Sanjaya
  2023-05-24 11:48 ` Zi Yan
  2023-05-24 12:58 ` Fwd: " Bagas Sanjaya
  0 siblings, 2 replies; 7+ messages in thread
From: Bagas Sanjaya @ 2023-05-24 10:58 UTC (permalink / raw)
  To: Linux Kernel Mailing List, Linux PowerPC,
	Linux Memory Management List, Linux Regressions
  Cc: Kirill A. Shutemov, Michael Ellerman, Zi Yan, Andrew Morton,
	doru iorgulescu, Nicholas Piggin, Christophe Leroy,
	Fabiano Rosas, Athira Rajeev, Disha Goel

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

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
  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
  2023-05-24 12:58 ` Fwd: " Bagas Sanjaya
  1 sibling, 0 replies; 7+ messages in thread
From: Zi Yan @ 2023-05-24 11:48 UTC (permalink / raw)
  To: Bagas Sanjaya
  Cc: Linux Kernel Mailing List, Linux PowerPC,
	Linux Memory Management List, Linux Regressions,
	Kirill A. Shutemov, Michael Ellerman, Andrew Morton,
	doru iorgulescu, Nicholas Piggin, Christophe Leroy,
	Fabiano Rosas, Athira Rajeev, Disha Goel

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
  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
@ 2023-05-24 12:58 ` Bagas Sanjaya
       [not found]   ` <CA+39qUjOA53UO4oYOzrUJqdYq8A3hbnnxpSV8nfqh0T5KiNL9A@mail.gmail.com>
  2023-05-24 15:03   ` Michael Ellerman
  1 sibling, 2 replies; 7+ messages in thread
From: Bagas Sanjaya @ 2023-05-24 12:58 UTC (permalink / raw)
  To: Linux Kernel Mailing List, Linux PowerPC,
	Linux Memory Management List, Linux Regressions
  Cc: Kirill A. Shutemov, Michael Ellerman, Zi Yan, Andrew Morton,
	doru iorgulescu, Nicholas Piggin, Christophe Leroy,
	Fabiano Rosas, Athira Rajeev, Disha Goel

On 5/24/23 17:58, Bagas Sanjaya wrote:
> 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
> 

From bugzilla [1], the reporter had successfully tried the proposed
kernel config fix, so:

#regzbot resolve: reducing CONFIG_ARCH_FORCE_MAX_ORDER to 8 resolves the regression

Thanks for all who participates in this regression report!

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217477#c8

-- 
An old man doll... just what I always wanted! - Clara


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
       [not found]   ` <CA+39qUjOA53UO4oYOzrUJqdYq8A3hbnnxpSV8nfqh0T5KiNL9A@mail.gmail.com>
@ 2023-05-24 13:39     ` Bagas Sanjaya
  0 siblings, 0 replies; 7+ messages in thread
From: Bagas Sanjaya @ 2023-05-24 13:39 UTC (permalink / raw)
  To: Doru Iorgulescu
  Cc: Linux Kernel Mailing List, Linux PowerPC,
	Linux Memory Management List, Linux Regressions,
	Kirill A. Shutemov, Michael Ellerman, Zi Yan, Andrew Morton,
	Nicholas Piggin, Christophe Leroy, Fabiano Rosas, Athira Rajeev,
	Disha Goel

On 5/24/23 20:11, Doru Iorgulescu wrote:
> Glad to hear it! 
> Thank you

tl;dr:

> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> A: No.
> Q: Should I include quotations after my reply?
> 
> http://daringfireball.net/2007/07/on_top

(IOW, I have no idea what you're referring to. Please stop top-posting;
reply inline with appropriate context instead.)

Also, don't send HTML emails as many mailing lists (including LKML)
don't like it.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
  2023-05-24 12:58 ` Fwd: " Bagas Sanjaya
       [not found]   ` <CA+39qUjOA53UO4oYOzrUJqdYq8A3hbnnxpSV8nfqh0T5KiNL9A@mail.gmail.com>
@ 2023-05-24 15:03   ` Michael Ellerman
  2023-05-25  0:57     ` Bagas Sanjaya
       [not found]     ` <CA+39qUjP48n=EwqHzwdGkBE8SC-nTNZHZxEfG4r4hWC-5Bg4HA@mail.gmail.com>
  1 sibling, 2 replies; 7+ messages in thread
From: Michael Ellerman @ 2023-05-24 15:03 UTC (permalink / raw)
  To: Bagas Sanjaya, Linux Kernel Mailing List, Linux PowerPC,
	Linux Memory Management List, Linux Regressions
  Cc: Kirill A. Shutemov, Zi Yan, Andrew Morton, doru iorgulescu,
	Nicholas Piggin, Christophe Leroy, Fabiano Rosas, Athira Rajeev,
	Disha Goel

Bagas Sanjaya <bagasdotme@gmail.com> writes:
> On 5/24/23 17:58, Bagas Sanjaya wrote:
>> 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
>> 
>
> From bugzilla [1], the reporter had successfully tried the proposed
> kernel config fix, so:
>
> #regzbot resolve: reducing CONFIG_ARCH_FORCE_MAX_ORDER to 8 resolves the regression

Should be fixed properly by:

https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20230519113806.370635-1-mpe@ellerman.id.au/

Which is in powerpc-fixes as 358e526a1648.

cheers

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
  2023-05-24 15:03   ` Michael Ellerman
@ 2023-05-25  0:57     ` Bagas Sanjaya
       [not found]     ` <CA+39qUjP48n=EwqHzwdGkBE8SC-nTNZHZxEfG4r4hWC-5Bg4HA@mail.gmail.com>
  1 sibling, 0 replies; 7+ messages in thread
From: Bagas Sanjaya @ 2023-05-25  0:57 UTC (permalink / raw)
  To: Michael Ellerman, Linux Kernel Mailing List, Linux PowerPC,
	Linux Memory Management List, Linux Regressions
  Cc: Kirill A. Shutemov, Zi Yan, Andrew Morton, doru iorgulescu,
	Nicholas Piggin, Christophe Leroy, Fabiano Rosas, Athira Rajeev,
	Disha Goel

[-- Attachment #1: Type: text/plain, Size: 381 bytes --]

On Thu, May 25, 2023 at 01:03:22AM +1000, Michael Ellerman wrote:
> Should be fixed properly by:
> 
> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20230519113806.370635-1-mpe@ellerman.id.au/
> 
> Which is in powerpc-fixes as 358e526a1648.

Telling regzbot:

#regzbot fix: 358e526a1648cd

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
       [not found]     ` <CA+39qUjP48n=EwqHzwdGkBE8SC-nTNZHZxEfG4r4hWC-5Bg4HA@mail.gmail.com>
@ 2023-05-29  8:24       ` Bagas Sanjaya
  0 siblings, 0 replies; 7+ messages in thread
From: Bagas Sanjaya @ 2023-05-29  8:24 UTC (permalink / raw)
  To: Doru Iorgulescu, Michael Ellerman
  Cc: Linux Kernel Mailing List, Linux PowerPC,
	Linux Memory Management List, Linux Regressions,
	Kirill A. Shutemov, Zi Yan, Andrew Morton, Nicholas Piggin,
	Christophe Leroy, Fabiano Rosas, Athira Rajeev, Disha Goel

[-- Attachment #1: Type: text/plain, Size: 306 bytes --]

On Wed, May 24, 2023 at 06:13:52PM +0300, Doru Iorgulescu wrote:
> Awesome, thanks!

tl;dr: see [1].

(Hey, looks like complimenting noise here.)

[1]: https://lore.kernel.org/regressions/5df92692-296e-3956-24fa-2bd439337953@gmail.com/

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2023-05-29  8:24 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2023-05-24 12:58 ` Fwd: " 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

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).