On 12/3/25 23:05, David Hildenbrand (Red Hat) wrote:
On 12/4/25 03:34, Shuah Khan wrote:
On 12/3/25 18:06, Guenter Roeck wrote:
On 12/3/25 14:16, Shuah Khan wrote:
CONFIG_RANDSTRUCT is disabled and so are the GCC_PLUGINS in my config.
I guess that would have been too easy...
I am also seeing issues with cloning kernel.org repos on my system after
a recent update:
remote: Enumerating objects: 11177736, done.
remote: Counting objects: 100% (1231/1231), done.
remote: Compressing objects: 100% (624/624), done.
remote: Total 11177736 (delta 855), reused 781 (delta 606), pack-reused
11176505 (from 1)
Receiving objects: 100% (11177736/11177736), 3.01 GiB | 7.10 MiB/s, done.
Resolving deltas: 100% (9198323/9198323), done.
fatal: did not receive expected object 0002003e951b5057c16de5a39140abcbf6e44e50
fatal: fetch-pack: invalid index-pack output
Linus, Andrew, and David,
Finally figured this out. I narrowed it to to be the HAVE_GIGANTIC_FOLIOS
support that went into Linux 6.18-rc6 in this commit:
From 39231e8d6ba7f794b566fd91ebd88c0834a23b98 Mon Sep 17 00:00:00 2001
From: "David Hildenbrand (Red Hat)" <[email protected]>
Date: Fri, 14 Nov 2025 22:49:20 +0100
Subject: [PATCH] mm: fix MAX_FOLIO_ORDER on powerpc configs with hugetlb
Unsuspected and confusing :(
This commit has impact on all architectures, not a narrow scoped
powerpc only thing - it enables HAVE_GIGANTIC_FOLIOS on x86_64
and changes the common code that determines MAX_FOLIO_ORDER in
include/linux/mm.h
Let me take a look at reply on the revert.
Sounds good. Reverting or finding a fix is good with me. It definitely
impacted two of my systems and the problem was introduced in
Linux 6.18-rc6 and is in Linux 6.18.
thanks,
-- Shuah
