]> git.proxmox.com Git - mirror_ubuntu-eoan-kernel.git/commit
x86/xen: Return from panic notifier
authorBoris Ostrovsky <boris.ostrovsky@oracle.com>
Mon, 30 Sep 2019 20:44:41 +0000 (16:44 -0400)
committerStefan Bader <stefan.bader@canonical.com>
Tue, 12 Nov 2019 17:47:11 +0000 (18:47 +0100)
commitcf07ab7a91d7a20c1797c7a460abcfe6693c7dbc
tree54c0c7f0feb9a39efbcfa1192c65d3f0fee155e6
parent3654c982068865be4d66f442157a60b033f913fc
x86/xen: Return from panic notifier

BugLink: https://bugs.launchpad.net/bugs/1851550
[ Upstream commit c6875f3aacf2a5a913205accddabf0bfb75cac76 ]

Currently execution of panic() continues until Xen's panic notifier
(xen_panic_event()) is called at which point we make a hypercall that
never returns.

This means that any notifier that is supposed to be called later as
well as significant part of panic() code (such as pstore writes from
kmsg_dump()) is never executed.

There is no reason for xen_panic_event() to be this last point in
execution since panic()'s emergency_restart() will call into
xen_emergency_restart() from where we can perform our hypercall.

Nevertheless, we will provide xen_legacy_crash boot option that will
preserve original behavior during crash. This option could be used,
for example, if running kernel dumper (which happens after panic
notifiers) is undesirable.

Reported-by: James Dingwall <james@dingwall.me.uk>
Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Signed-off-by: Connor Kuehl <connor.kuehl@canonical.com>
Signed-off-by: Khalid Elmously <khalid.elmously@canonical.com>
Documentation/admin-guide/kernel-parameters.txt
arch/x86/xen/enlighten.c