Hello Pratyush,
On Fri, Jan 02, 2026 at 09:17:27PM +0100, Pratyush Yadav wrote:
> > Subject: [PATCH v2 1/2] kexec: history: track previous kernel version
>
> Nit: please use the prefix "kho: " for KHO patches.
ack.
> On Fri, Jan 02 2026, Breno Leitao wrote:
> > Add CONFIG_KEXEC_HISTORY to store and display the kernel version from
> > the previous kexec boot.
> >
> > When enabled, the current kernel's release string is saved to the
> > "previous-release" property in the KHO device tree before kexec. On
> > the next boot, if this property exists, the previous kernel version
> > is retrieved and printed during early boot.
> >
> > This helps diagnose bugs that only manifest when kexecing from
> > specific kernel versions, making it easier to correlate crashes with
> > the kernel that initiated the kexec.
>
> Why can't you use journalctl to figure out which kernel was running
> previously?
This is a good question, this is why this doesn't work for me:
1) in some cases you cannot rely on systemd infrastructure.
- This is very common when you have linux as the boot loader, which
basically boot linux (UEFI -> Bootloader/linux -> kexec -> target linux)
- In these cases, the bootloader doesn't have write access to the
filesyste/journal
- This is becoming more and more common. For instance, at Meta, Linux
is the default bootloader.
2) in some of the bugs I've listed earlier, the machine doesn't even get
to userspace before the crash. For instance, in the bug fixed by
commit 77d48d39e991 ("efistub/tpm: Use ACPI reclaim memory for event
log to avoid corruption"), the kernel was not reach userspace/init,
thus, it would not be possible to run journalctl.
Thanks for the review,
--breno
