From: Shuah Khan <skhan@linuxfoundation•org>
To: "David Hildenbrand (Red Hat)" <david@kernel•org>,
akpm@linux-foundation•org
Cc: maddy@linux•ibm.com, mpe@ellerman•id.au, npiggin@gmail•com,
christophe.leroy@csgroup•eu, lorenzo.stoakes@oracle•com,
Liam.Howlett@oracle•com, vbabka@suse•cz, rppt@kernel•org,
surenb@google•com, mhocko@suse•com, masahiroy@kernel•org,
linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org,
linux-mm@kvack•org, Shuah Khan <skhan@linuxfoundation•org>
Subject: Re: [PATCH] Revert "mm: fix MAX_FOLIO_ORDER on powerpc configs with hugetlb"
Date: Thu, 4 Dec 2025 16:23:36 -0700 [thread overview]
Message-ID: <317deba2-e560-44ed-a9f7-3c6fdc446b6d@linuxfoundation.org> (raw)
In-Reply-To: <51d8549e-b084-498e-84c0-76fd3de116cb@kernel.org>
On 12/4/25 15:16, David Hildenbrand (Red Hat) wrote:
> On 12/4/25 03:33, Shuah Khan wrote:
>> This reverts commit 39231e8d6ba7f794b566fd91ebd88c0834a23b98.
>>
>> Enabling HAVE_GIGANTIC_FOLIOS broke kernel build and git clone on two
>> systems. git fetch-pack fails when cloning large repos and make hangs
>> or errors out of Makefile.build with Error: 139.
>
> Looking at the last part, "Error 139" was confirmed to be fixed in 6.18, right? At least reading [1] there I find
>
> "it was issue of 6.18.0-rc6 kernel itself. After switching to default Arch Linux kernel build went without problem and I'm now on 6.18 stable kernel."
>
> Did you mange to report the make issue you reported here [2] on 6.18 as well, or only pre 6.18-rc7?
The problems I saw were on rc6. See below.
Repeating what I said on the thread so we are all in the
loop and on the same page. It took me a bit of time to
retest on two systems.
Both my systems were running rc6 - I was stuck in a state
where I was able to rebase to rc7 and then 6.18, but could
never build either one.
When I suspected rc6 to be the problem, I booted rc5 and compiled 6.18
after reverting 39231e8d6ba based on config file changes between rc5
and rc6.
I retested on both systems on 6.18 making sure I have 5bebe8de19264
and 39231e8d6ba in there. I cloned linux_next and built it on both.
I didn't see any problems on 6.18. Having said that, It might make
sense to hold off on including 39231e8d6ba in 6.18 so there is more
time to test beyond 2 rc cycles. That is for you all to decide.
thanks,
-- Shuah
next prev parent reply other threads:[~2025-12-04 23:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 2:33 [PATCH] Revert "mm: fix MAX_FOLIO_ORDER on powerpc configs with hugetlb" Shuah Khan
2025-12-04 6:17 ` David Hildenbrand (Red Hat)
2025-12-04 6:35 ` Mike Rapoport
2025-12-04 17:03 ` Shuah Khan
2025-12-04 19:38 ` David Hildenbrand (Red Hat)
2025-12-04 20:59 ` Mike Rapoport
2025-12-04 21:27 ` Mike Rapoport
2025-12-04 21:57 ` Andrew Morton
2025-12-04 22:12 ` David Hildenbrand (Red Hat)
2025-12-05 7:01 ` Mike Rapoport
2025-12-05 7:05 ` David Hildenbrand (Red Hat)
2025-12-05 7:41 ` Christophe Leroy (CS GROUP)
2025-12-05 18:19 ` Andrew Morton
2025-12-04 22:16 ` David Hildenbrand (Red Hat)
2025-12-04 23:23 ` Shuah Khan [this message]
2025-12-05 6:50 ` Mike Rapoport
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=317deba2-e560-44ed-a9f7-3c6fdc446b6d@linuxfoundation.org \
--to=skhan@linuxfoundation$(echo .)org \
--cc=Liam.Howlett@oracle$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=david@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=lorenzo.stoakes@oracle$(echo .)com \
--cc=maddy@linux$(echo .)ibm.com \
--cc=masahiroy@kernel$(echo .)org \
--cc=mhocko@suse$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=rppt@kernel$(echo .)org \
--cc=surenb@google$(echo .)com \
--cc=vbabka@suse$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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