The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: "Longia, Amandeep Kaur" <AmandeepKaur.Longia@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org, lance.yang@linux.dev, will@kernel.org,
	b-padhi@ti.com, aishwarya.tcv@arm.com, broonie@kernel.org,
	Raghavendra.KodsaraThimmappa@amd.com,
	Jan Polensky <japo@linux.ibm.com>
Subject: Re: [BUG] General Protection Faults During Git Clone and Kernel Build on Latest Kernel
Date: Wed, 19 Nov 2025 11:58:23 +0000	[thread overview]
Message-ID: <aR2w3y1TxJqp2r5N@arm.com> (raw)
In-Reply-To: <ff2038c3-a14f-45e4-8289-f7367d702ab9@kernel.org>

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

  reply	other threads:[~2025-11-19 11:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 12:08 [BUG] General Protection Faults During Git Clone and Kernel Build on Latest Kernel Longia, Amandeep Kaur
2025-11-17 12:24 ` David Hildenbrand (Red Hat)
2025-11-19 11:58   ` Catalin Marinas [this message]
2025-11-19 12:01     ` David Hildenbrand (Red Hat)
2025-11-19 12:52     ` Catalin Marinas

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=aR2w3y1TxJqp2r5N@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=AmandeepKaur.Longia@amd.com \
    --cc=Raghavendra.KodsaraThimmappa@amd.com \
    --cc=aishwarya.tcv@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=b-padhi@ti.com \
    --cc=broonie@kernel.org \
    --cc=david@kernel.org \
    --cc=japo@linux.ibm.com \
    --cc=lance.yang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@kernel.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