Re: [PATCH v2 6/6] x86/vmware: Report guest crashes after kmsg dumpers

[sashiko-bot]

> 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 pre-kdump log sender.
> 
> 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@xxxxxxxxxxxx
> Co-developed-by: Brennan Lamoreaux <brennan.lamoreaux@xxxxxxxxxxxx>
> Signed-off-by: Brennan Lamoreaux <brennan.lamoreaux@xxxxxxxxxxxx>
> Co-developed-by: Alexey Makhalov <alexey.makhalov@xxxxxxxxxxxx>
> Signed-off-by: Alexey Makhalov <alexey.makhalov@xxxxxxxxxxxx>
> Signed-off-by: Zack Rusin <zack.rusin@xxxxxxxxxxxx>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1790014793.git.zack.rusin@xxxxxxxxxxxx?part=6