From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 41E5C2F5A22 for ; Thu, 4 Dec 2025 20:59:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764881959; cv=none; b=UuMGM/NnSO1LM5Ptn8uO92j5DryGU33/P8NFLJARk27kMD0lTHnKRsR/4f9fas3JbYUiMVZogS1CielReKuH1OAsDz1aG1Yg7oQPLE+naR8wKZzt0OE5wBGraskH9cGUmTQRRcxJJVdVZ+ejIDjNvHpCx6uaMLM74vZP4W3h4aE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764881959; c=relaxed/simple; bh=4O9Ah99qQTol32t/P1TpxoZv82j3pnx84+70Fb5YdUY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=JDx4s5fbGW/8wpzZZZ0NXEkFmCiEoz/NgWz515UAY1lvtrIiXnebIurVQo/H95OGzi2i4/+cdD6uNY9xoKdQrGbJj4ooy0ZR11c3KK/OVxgxGm3nGzTIT3+Q8Ox1OXfqgDlJ01BIUNcHgBnyk4ILsb+z5wWF11BQFbws1X6BOrw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=tA78S6gr; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="tA78S6gr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 90672C113D0; Thu, 4 Dec 2025 20:59:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1764881958; bh=4O9Ah99qQTol32t/P1TpxoZv82j3pnx84+70Fb5YdUY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tA78S6gr+Qh7bTbz1ZeQsKn2yGl8q4Zf+nVGht3F99N8vJ/cfaY3BEbh1wNMwik04 6yI4dWNE7oOeGtCS8nDKTWo023FfpA2DYMkTLCkIv2pNSHah+uEDPIdVrQ37UbYhHa PEmBvcA84WFCfGaks4Q6Kk3d796ZNH8pgOvqH3/bZLB/x2gqMu5lY17lL5C+mbbxG0 l+fkHGM4GZfABuGw+vc9NNNnO7Zn6vH+qVtRfH9DEqIMQF0/UAxuZKXiAqcoKofPwq t5jjTTwFiUSnt6w8ox3aYTVelANQ+D9kaLir7yFW1Pta6MLisJFL68Lpv0Cijor3wI xZH0ghAZwUgMQ== Date: Thu, 4 Dec 2025 22:59:10 +0200 From: Mike Rapoport To: Shuah Khan Cc: "David Hildenbrand (Red Hat)" , 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" Message-ID: References: <20251204023358.54107-1-skhan@linuxfoundation.org> <0b007374-1058-487c-8033-4f0d2830dc89@kernel.org> <78af7da4-d213-42c6-8ca6-c2bdca81f233@linuxfoundation.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 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.