Re: hunting memory corruption bug in 6.18.x
From: Nikola Ciprich
Date: Sun Oct 04 2026 - 14:47:10 EST
On Fri, Oct 02, 2026 at 03:02:48PM -0700, Borislav Petkov wrote:
> On Fri, Oct 02, 2026 at 04:55:39PM +0200, Nikola Ciprich wrote:
> > I'll leave it running for few hours, and report back. If I'm able to reproduce,
> > I'll try recommended workarounds and report as well.
>
> I'll venture a guess here and say that Matt's reproducer won't trigger on your
> machines.
and you're right :(
>
> Just to rule out any other issues which got fixed in the meantime, can you try
> mainline Linux and see if you can reproduce your observation with it?
that'll be very complicated in production.. it'd help a lot if we could reproduce
it in lab again..
I guess we'll add more windows guests and more load in them and see if we can reproduce
it in lab..
>
> If so, you could share your crash core along with debug kernels yadda yadda so
> that I can poke at it.
>
> And before you do, make sure you have the latest BIOS and microcode installed on
> that machine.
>
> Also, where can I find full dmesg and /proc/cpuinfo from those machines which
> trigger this?
I'll gather it all and put it on storage to download tomorrow.
cheers
nik
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
--
Ing. Nikola CIPRICH
technický ředitel
+420 591 166 214
+420 777 093 799
nikola.ciprich@xxxxxxxxxxx
www.linuxbox.cz