On Wed, Dec 31, 2025 at 12:14:47PM -0800, [email protected] wrote: > From: Michael Kelley <[email protected]> > > hv_kmsg_dump() currently skips the panic notification entirely if it > doesn't get any message bytes to pass to Hyper-V due to an error from > kmsg_dump_get_buffer(). Skipping the notification is undesirable because > it leaves the Hyper-V host uncertain about the state of a panic'ed guest. > > Fix this by always doing the panic notification, even if bytes_written > is zero. Also ensure that bytes_written is initialized, which fixes a > kernel test robot warning. The warning is actually bogus because > kmsg_dump_get_buffer() happens to set bytes_written even if it fails, and > in the kernel test robot's CONFIG_PRINTK not set case, hv_kmsg_dump() is > never called. But do the initialization for robustness and to quiet the > static checker. > > Fixes: 9c318a1d9b50 ("Drivers: hv: move panic report code from vmbus to hv > early init code") > Reported-by: kernel test robot <[email protected]> > Reported-by: Dan Carpenter <[email protected]> > Closes: https://lore.kernel.org/all/[email protected]/ > Signed-off-by: Michael Kelley <[email protected]>
Applied. Thanks.
