All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: "David Hildenbrand (Red Hat)" <david@kernel.org>,
	akpm@linux-foundation.org, 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, surenb@google.com,
	mhocko@suse.com, masahiroy@kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] Revert "mm: fix MAX_FOLIO_ORDER on powerpc configs with hugetlb"
Date: Thu, 4 Dec 2025 22:59:10 +0200	[thread overview]
Message-ID: <aTH2HqxZjmFHWlSJ@kernel.org> (raw)
In-Reply-To: <78af7da4-d213-42c6-8ca6-c2bdca81f233@linuxfoundation.org>

On Thu, Dec 04, 2025 at 10:03:09AM -0700, Shuah Khan wrote:
> On 12/3/25 23:35, Mike Rapoport wrote:
> > On Thu, Dec 04, 2025 at 07:17:06AM +0100, David Hildenbrand (Red Hat) wrote:
> > > >
> > > > The blow is is one of the git clone failures:
> > > > 
> > > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux_6.19
> > > > Cloning into 'linux_6.19'...
> > > > remote: Enumerating objects: 11173575, done.
> > > > remote: Counting objects: 100% (785/785), done.
> > > > remote: Compressing objects: 100% (373/373), done.
> > > > remote: Total 11173575 (delta 534), reused 505 (delta 411), pack-reused 11172790 (from 1)
> > > > Receiving objects: 100% (11173575/11173575), 3.00 GiB | 7.08 MiB/s, done.
> > > > Resolving deltas: 100% (9195212/9195212), done.
> > > > fatal: did not receive expected object 0002003e951b5057c16de5a39140abcbf6e44e50
> > > > fatal: fetch-pack: invalid index-pack output
> > > 
> > > If I would have to guess, these symptoms match what we saw between commit
> > > adfb6609c680 ("mm/huge_memory: initialise the tags of the huge zero folio")
> > > and commit 5bebe8de1926 ("mm/huge_memory: Fix initialization of huge zero folio").
> > > 
> > > 5bebe8de1926 went into v6.18-rc7.
> > > 
> > > Just to be sure, are you sure we were able to reproduce this issue with a
> > > v6.18-rc7 or even v6.18 that contains 5bebe8de1926?
> > > 
> > > Bisecting might give you wrong results, as the problems of adfb6609c680 do not
> > > reproduce reliably.
> > I can confirm that bisecting gives odd results between v6.18-rc5 and
> > v6.18-rc6. I was seeing failures in some tests, bisected a few times and
> > got a bunch of bogus commits including 3470715e5c22 ("MAINTAINERS: update
> > David Hildenbrand's email address") :)
> 
> I am sure this patch is the cause oh the problems I have seen on my two
> systems. Reverting this commit solved issues since this commit does
> impact all architectures enabling HAVE_GIGANTIC_FOLIOS if the conditions
> are right.

The issue reproduces for me with 39231e8d6ba7 reverted as well.
If I run git clone <linux repo> in a VM with 2G of ram it becomes
unresponsive at about 40% of "Receiving objects" and than git errors out
with "invalid index-pack output"

-- 
Sincerely yours,
Mike.


  parent reply	other threads:[~2025-12-04 20:59 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 [this message]
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
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=aTH2HqxZjmFHWlSJ@kernel.org \
    --to=rppt@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=david@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=maddy@linux.ibm.com \
    --cc=masahiroy@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.