linux-kernel - RE: Machine check recovery broken in v6.9-rc1

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] [thread-next>] [day] [month] [year] [list]

Date: Fri, 5 Apr 2024 15:05:17 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: David Hildenbrand <david@...hat.com>, Borislav Petkov <bp@...en8.de>,
	Yazen Ghannam <yazen.ghannam@....com>, Miaohe Lin <linmiaohe@...wei.com>,
	Naoya Horiguchi <naoya.horiguchi@....com>, "linux-mm@...ck.org"
	<linux-mm@...ck.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: RE: Machine check recovery broken in v6.9-rc1

>> kernel BUG at include/linux/swapops.h:119
>> 
>> 117 static inline unsigned long swp_offset_pfn(swp_entry_t entry)
>> 118 {
>> 119         VM_BUG_ON(!is_pfn_swap_entry(entry));
>> 120         return swp_offset(entry) & SWP_PFN_MASK;
>> 121 }
>> 
>
> Do you have the full backtrace?

It's very garbled because multiple CPUs seem to be logging to the console together.

I've also got some more details.

1) Problems with recovery go back further than v6.8. Still looking to pin down where it started.
   v6.0 seems good (can run hundreds of injections + consumptions).
2) It's connected to a BIOS setting that enables APEI logging. If I disable that, current
   kernels don't have problems. v6.0 runs OK with this setting on or off.

I'm bisecting to find where the APEI issue begins.

-Tony