From: Michael Ellerman <mpe@ellerman.id.au>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
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>
Cc: doru iorgulescu <doru.iorgulescu1@gmail.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Fabiano Rosas <farosas@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>, Zi Yan <ziy@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Disha Goel <disgoel@linux.vnet.ibm.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: Fwd: ./include/linux/mmzone.h:1735:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE (v6.4-rc3 build regression)
Date: Thu, 25 May 2023 01:03:22 +1000 [thread overview]
Message-ID: <87bki9ai11.fsf@mail.lhotse> (raw)
In-Reply-To: <5d22e1e9-0307-3664-8b4a-99caaaaa4315@gmail.com>
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
next prev parent reply other threads:[~2023-05-24 15:04 UTC|newest]
Thread overview: 9+ 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
2023-05-24 12:58 ` Fwd: " Bagas Sanjaya
2023-05-24 13:11 ` Doru Iorgulescu
2023-05-24 13:39 ` Bagas Sanjaya
2023-05-24 15:03 ` Michael Ellerman [this message]
2023-05-24 15:13 ` Doru Iorgulescu
2023-05-29 8:24 ` Bagas Sanjaya
2023-05-25 0:57 ` 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=87bki9ai11.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=bagasdotme@gmail.com \
--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=npiggin@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=ziy@nvidia.com \
/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).