[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d22e1e9-0307-3664-8b4a-99caaaaa4315@gmail.com>
Date: Wed, 24 May 2023 19:58:16 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux PowerPC <linuxppc-dev@...ts.ozlabs.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Linux Regressions <regressions@...ts.linux.dev>
Cc: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Michael Ellerman <mpe@...erman.id.au>, Zi Yan <ziy@...dia.com>,
Andrew Morton <akpm@...ux-foundation.org>,
doru iorgulescu <doru.iorgulescu1@...il.com>,
Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Fabiano Rosas <farosas@...ux.ibm.com>,
Athira Rajeev <atrajeev@...ux.vnet.ibm.com>,
Disha Goel <disgoel@...ux.vnet.ibm.com>
Subject: Re: Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator
MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
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
Powered by blists - more mailing lists