linux-kernel - Re: [RFC PATCH 2/4] mm: Add support for unaccepted memory hotplug

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]

Message-ID: <ed2fd8ed5d3c64e0e57e0d38fe6e3d712f22d13f.camel@surriel.com>
Date: Wed, 03 Dec 2025 10:00:03 -0500
From: Rik van Riel <riel@...riel.com>
To: "David Hildenbrand (Red Hat)" <david@...nel.org>, Borislav Petkov
	 <bp@...en8.de>, Kiryl Shutsemau <kas@...nel.org>
Cc: "Pratik R. Sampat" <prsampat@....com>, linux-mm@...ck.org, 
	linux-coco@...ts.linux.dev, linux-efi@...r.kernel.org, x86@...nel.org, 
	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com, 
	dave.hansen@...ux.intel.com, ardb@...nel.org, akpm@...ux-foundation.org, 
	osalvador@...e.de, thomas.lendacky@....com, michael.roth@....com
Subject: Re: [RFC PATCH 2/4] mm: Add support for unaccepted memory hotplug

On Fri, 2025-11-28 at 10:30 +0100, David Hildenbrand (Red Hat) wrote:
> On 11/27/25 19:12, Borislav Petkov wrote:
> > 
> > None of that matters if you kexec the same kernels.
> > 
> > IOW, for some reason you want to be able to kexec different
> > kernels. The
> > question is why do we care?
> 
> kexecing the same kernel is typically used for kdump purposes.
> 
> kexecing different kernels is used for all sorts of things 
> (live-upgrade, grub-emu come to mind). It's quite common to kexec 
> different kernels, or maybe I misunderstood the question here?
> 

Even for kdump it is not unusual to use a different
kernel.

When working on kernel code, getting a proper crash
dump can really help figure out where my code went
wrong.

It helps if the kdump kernel doesn't have the same
broken code that my test kernel does :)

-- 
All Rights Reversed.