From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: "Longia, Amandeep Kaur" <AmandeepKaur.Longia@amd.com>,
catalin.marinas@arm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org
Cc: 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: Mon, 17 Nov 2025 13:24:43 +0100 [thread overview]
Message-ID: <ff2038c3-a14f-45e4-8289-f7367d702ab9@kernel.org> (raw)
In-Reply-To: <9401208f-2db1-4397-a615-a03fd7520e53@amd.com>
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
--
Cheers
David
next prev parent reply other threads:[~2025-11-17 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 12:08 Longia, Amandeep Kaur
2025-11-17 12:24 ` David Hildenbrand (Red Hat) [this message]
2025-11-19 11:58 ` Catalin Marinas
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=ff2038c3-a14f-45e4-8289-f7367d702ab9@kernel.org \
--to=david@kernel.org \
--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=catalin.marinas@arm.com \
--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
all inboxes | Powered by JetHome®