[PATCH 0/3][BFGH][linux] Fix kdump failures
Thadeu Lima de Souza Cascardo
cascardo at canonical.com
Thu May 6 21:28:24 UTC 2021
On Thu, May 06, 2021 at 02:59:42PM -0600, Tim Gardner wrote:
> BugLink: https://bugs.launchpad.net/bugs/1927518
>
> [Impact]
>
> Microsoft has reported that a customer is not able to acquire a kdump
> when a guest crashes.
>
> The following 3 patches fix the issue. Patch #1 solves a problem where the
> “Unable to send packet via vmbus” message is output continuously. But with
> that problem fixed, the second problem can occur where the kdump kernel
> panics due to receiving an unexpected VMbus UNLOAD complete message.
>
> Patch #2 prevents the UNLOAD complete message from ever occurring in the
> kdump kernel. But if the UNLOAD complete message does occur at some
> unexpected time, Patch #3 prevents it from causing a panic.
>
> [Test Plan]
>
> Cause a guest kernel crash and acquire a kdump.
>
> [Where problems could occur]
>
> The increased Hyper-V timeout could have side effects.
>
> [Other Info]
>
> If these patches are deemed unsuitable for master, then I would at least like to have them
> applied to fgh:linux-azure and bionic:linux-azure-4.15
>
> The Bionic patches are also all clean cherry-picks, but 'git am' would not apply
> the third of the FGH patches. There is likely some option to 'git am' that I'm
> too lazy to find or remember.
Hey, Tim.
All seem good here. The commits seem sensible and are restricted to Hyper-V.
You forgot no note the series to which the individual patches would apply,
though.
Care to resend?
Thanks.
Cascardo.
More information about the kernel-team
mailing list