OSDN Git Service

x86/xen: Return from panic notifier
authorBoris Ostrovsky <boris.ostrovsky@oracle.com>
Mon, 30 Sep 2019 20:44:41 +0000 (16:44 -0400)
committerBoris Ostrovsky <boris.ostrovsky@oracle.com>
Mon, 7 Oct 2019 21:53:30 +0000 (17:53 -0400)
commitc6875f3aacf2a5a913205accddabf0bfb75cac76
treeab2ad24560746f3b179b5c3d48ee8461a1eee0d9
parenta8fabb38525c51a094607768bac3ba46b3f4a9d5
x86/xen: Return from panic notifier

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>
Documentation/admin-guide/kernel-parameters.txt
arch/x86/xen/enlighten.c