linux-kernel - Re: [BUG] General Protection Faults During Git Clone and Kernel Build on Latest Kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aR29iEjLwyGV9Mus@arm.com>
Date: Wed, 19 Nov 2025 12:52:24 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: "David Hildenbrand (Red Hat)" <david@...nel.org>
Cc: "Longia, Amandeep Kaur" <AmandeepKaur.Longia@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	akpm@...ux-foundation.org, lance.yang@...ux.dev, will@...nel.org,
	b-padhi@...com, aishwarya.tcv@....com, broonie@...nel.org,
	Raghavendra.KodsaraThimmappa@....com,
	Jan Polensky <japo@...ux.ibm.com>
Subject: Re: [BUG] General Protection Faults During Git Clone and Kernel
 Build on Latest Kernel

On Wed, Nov 19, 2025 at 11:58:27AM +0000, Catalin Marinas wrote:
> On Mon, Nov 17, 2025 at 01:24:43PM +0100, David Hildenbrand (Red Hat) wrote:
> > On 17.11.25 13:08, Longia, Amandeep Kaur wrote:
> > > Hi all,
> > > 
> > > We've encountered critical issues while running our CI pipeline on the
> > > latest kernel (v6.18-rc6), which involves cloning multiple repositories
> > > for testing and building the kernel. During this process, we observed
> > > two major issues:
> > 
> > Hi,
> > 
> > I observed something similar while testing on Friday between rc4 (good) and
> > rc5+ (bad).
> > 
> > I'm sure this it the known issue of adfb6609c6809e107ded9a1cd46f519c882e64ea
> > we discussed already here [1].
> > 
> > 
> > @Jan, can you send the fix out today? Otherwise I can take care of this so
> > we get this fixed asap.
> > 
> > [1] https://lkml.kernel.org/r/20251109003613.1461433-1-japo@linux.ibm.com
> 
> In the worst case, I think Andrew can just revert commit  adfb6609c680
> ("mm/huge_memory: initialise the tags of the huge zero folio"), we can
> fix it properly with a cc stable afterwards.
> 
> BTW, another quick fix (pretty much what arm64 does when MTE is off):
> 
> -------8<--------------------------
> diff --git a/include/linux/highmem.h b/include/linux/highmem.h
> index 105cc4c00cc3..2b848a66f150 100644
> --- a/include/linux/highmem.h
> +++ b/include/linux/highmem.h
> @@ -253,6 +253,7 @@ static inline void clear_highpage_kasan_tagged(struct page *page)
> 
>  static inline void tag_clear_highpage(struct page *page)
>  {
> +	clear_highpage(page);
>  }
> 
>  #endif

I now saw the long thread with Linus, it's all fixed upstream. Thanks!

-- 
Catalin