linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	akpm@linux-foundation.org
Cc: Alexander Deucher <Alexander.Deucher@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	amd-gfx@lists.freedesktop.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: Linux 6.18 amdgpu build error
Date: Thu, 4 Dec 2025 07:05:19 +0100	[thread overview]
Message-ID: <2bc690ca-fa57-46fa-949b-28b5441cd364@kernel.org> (raw)
In-Reply-To: <5af4522e-30ab-4eec-a861-c2760cdabd4f@linuxfoundation.org>

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)" <david@kernel.org>
> Date: Fri, 14 Nov 2025 22:49:20 +0100
> Subject: [PATCH] mm: fix MAX_FOLIO_ORDER on powerpc configs with hugetlb
> 

Unsuspected and confusing :(

Let me take a look at reply on the revert.

-- 
Cheers

David


  reply	other threads:[~2025-12-04  6:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <74032153-813a-4a40-8363-cce264f4d5ea@linuxfoundation.org>
     [not found] ` <1eb24816-530b-4470-8e58-ce7d8297996c@roeck-us.net>
     [not found]   ` <0425d7b4-76e4-4057-83a5-a7b17a051c54@linuxfoundation.org>
     [not found]     ` <ec77d11a-7613-4b75-8c9e-f2bba1595f0f@roeck-us.net>
     [not found]       ` <9d520a1d-0b8d-4d30-b29f-230fc0f92b8a@linuxfoundation.org>
     [not found]         ` <1f31b86d-283c-4878-92d0-ab90aed0c58d@roeck-us.net>
2025-12-04  2:34           ` Shuah Khan
2025-12-04  6:05             ` David Hildenbrand (Red Hat) [this message]
2025-12-04 17:40               ` Shuah Khan
2025-12-04 19:36                 ` Linus Torvalds
2025-12-04 19:45                   ` David Hildenbrand (Red Hat)
2025-12-04 23:20                     ` Shuah Khan
2025-12-04 23:23                       ` Linus Torvalds
2025-12-04 23:28                         ` Shuah Khan

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=2bc690ca-fa57-46fa-949b-28b5441cd364@kernel.org \
    --to=david@kernel.org \
    --cc=Alexander.Deucher@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@roeck-us.net \
    --cc=skhan@linuxfoundation.org \
    --cc=torvalds@linux-foundation.org \
    /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