[PATCH 6/9] kho: Expose rejected handovers that look like cold boots
sashiko-bot at kernel.org
sashiko-bot at kernel.org
Wed Nov 11 23:54:11 PST 2026
> At Meta, our rollout needs to stop if the new kernel rejects the KHO
> handover. For example, if it doesn't recognise the handover FDT's
> compatible string, it can boot normally with all the preserved state
> lost. LUO's incoming/state reads "none", as on a cold boot. We log
> "disabling KHO revival", but our fleet collector reads procfs and sysfs
> and can't rely on kernel logs from every host.
>
> Let's add /sys/kernel/kexec/kho_incoming/state so the collector can tell
> a rejected handover from an ordinary boot. "revived" means the kernel
> accepted the handover and completed the preserved memory map walk. LUO
> reports the outcome of restoring sessions separately.
>
> Signed-off-by: Chris Down <chris at chrisdown.name>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794383544.git.chris@chrisdown.name?part=6
More information about the kexec
mailing list