[PATCH v3 4/4] x86/vmware: Report guest crashes after kmsg dumpers

sashiko-bot at kernel.org sashiko-bot at kernel.org
Sun Nov 8 21:52:33 PST 2026


> VMware accepts a structured guest-crash event, but a host configured with
> backdoor.coredumpOnCrash may terminate the VM before the hypercall
> returns. Keep this event separate from the log sender, which runs
> earlier in panic.
> 
> Register a panic-only kmsg dumper with late_initcall_sync(), after built-in
> dumpers registered by then. Skip the event while a crash kernel is loaded
> so the host cannot terminate the guest before kdump saves its vmcore.
> 
> Issue the event at most once. With CONFIG_PRINTK=n, use a late INT_MIN
> panic notifier. An unexpected dumper registration failure with printk
> enabled leaves reporting disabled rather than overtaking working dumpers.
> 
> Link: https://lore.kernel.org/r/20260309235250.2611115-4-alexey.makhalov@broadcom.com
> Co-developed-by: Brennan Lamoreaux <brennan.lamoreaux at broadcom.com>
> Signed-off-by: Brennan Lamoreaux <brennan.lamoreaux at broadcom.com>
> Co-developed-by: Alexey Makhalov <alexey.makhalov at broadcom.com>
> Signed-off-by: Alexey Makhalov <alexey.makhalov at broadcom.com>
> Signed-off-by: Zack Rusin <zack.rusin at broadcom.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794201807.git.zack.rusin@broadcom.com?part=4




More information about the kexec mailing list