linux-kernel - [REGRESSION] Platforms supporting SGX fail to kexec due to 96c6b8f212a ("memblock: report failures when memblock_can

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

Message-ID: <ZY4T7YxrJZCxhMxx@a4bf019067fa.jf.intel.com>
Date: Thu, 28 Dec 2023 16:33:49 -0800
From: Ashok Raj <ashok.raj@...el.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>, LKML Mailing List
	<linux-kernel@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>,
	Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...el.com>, "Ingo
 Molnar" <mingo@...nel.org>, <regressions@...ts.linux.dev>
CC: Mike Rapoport <rppt@...nel.org>, Ashok Raj <ashok.raj@...el.com>
Subject: [REGRESSION] Platforms supporting SGX fail to kexec due to
 96c6b8f212a ("memblock: report failures when memblock_can_resize is not
 set")

Hi 

96c6b8f212a ("memblock: report failures when memblock_can_resize is not set")

Causes kexec failure. Backing out this change, kexec succeeds. Symptom is
it appears to hang, possibly hung at the panic. Although I have the
earlyprintk enabled, I don't see any console messages when new kernel
boots. 

Also tested turning off CONFIG_X86_SGX, the kernel with this commit
included also kexec's fine.

Booting from warm/cold reset has no issues. Only kexec to new kernel with
this change included and CONFIG_X86_SGX=y causes the kexec failure.

#regzbot introduced: 96c6b8f212a
-- 
Cheers,
Ashok