linux-kernel - Re: Kernel crash while doing chroot'ed grub2-mkconfig on qemu-emulated Nehalem CPU since late November 6.13 snapshot

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: <ddf33df9a8b5bd8593937a593d1d8472515b970a.camel@redhat.com>
Date: Tue, 14 Jan 2025 00:08:25 -0800
From: Adam Williamson <awilliam@...hat.com>
To: Mike Rapoport <rppt@...nel.org>
Cc: linux-kernel@...r.kernel.org, jforbes@...hat.com, mcgrof@...nel.org
Subject: Re: Kernel crash while doing chroot'ed grub2-mkconfig on
 qemu-emulated Nehalem CPU since late November 6.13 snapshot

On Mon, 2025-01-13 at 23:55 -0800, Adam Williamson wrote:
> On Mon, 2025-01-13 at 11:16 -0800, Adam Williamson wrote:
> > On Sun, 2025-01-12 at 10:47 -0800, Adam Williamson wrote:
> > > > 
> > > > I don't think that CPU flavour is important here. I'll greatly appreciate
> > > > your testing.
> > > 
> > > Update - I tried doing a quick build yesterday but the patch doesn't
> > > apply cleanly against our current Fedora Rawhide kernel. I'll look at
> > > it again tomorrow. Sorry for the delay.
> > 
> > OK, I've got a test build working now. Looks like `struct execmem_area
> > *area;` is not in Linus' current tree, I guess it's from your branch or
> > something? Fortunately I just had to drop that line from the patch and
> > it applies fine.
> 
> OK, so good news: initial testing of that patch (the
> `get_vm_area_page_order(vm) + PAGE_SHIFT` one) looks good. I've run it
> through 40 installs so far without a hang. Just as a sanity check, I
> also ran the non-patched kernel through 10 installs on the same openQA
> instance and it hung four times.
> 
> I'll run some more cycles tomorrow to be sure, but it looks good.
> Thanks!

BTW, I took a few minutes to look through a bunch of the failures, and
noticed that all the ones I checked seem to be on Xeon Gold 5218 or
Xeon Gold 6130 hosts. The older Xeon E5-2683v4 and Xeon E5-2680 hosts
don't seem to have any failures. Not sure if that's interesting/useful,
but thought I'd mention it.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@...stodon.org
https://www.happyassassin.net