From: Guilherme G. Piccoli <gpicc...@igalia.com> Sent: Wednesday, April 27,
2022 3:49 PM
>
> The goal of this new panic notifier is to allow its users to register
> callbacks to run very early in the panic path. This aims hypervisor/FW
> notification mechanisms as well as simple LED functions, and any other
> simple and safe mechanism that should run early in the panic path; more
> dangerous callbacks should execute later.
>
> For now, the patch is almost a no-op (although it changes a bit the
> ordering in which some panic notifiers are executed). In a subsequent
> patch, the panic path will be refactored, then the panic hypervisor
> notifiers will effectively run very early in the panic path.
>
> We also defer documenting it all properly in the subsequent refactor
> patch. While at it, we removed some useless header inclusions and
> fixed some notifiers return too (by using the standard NOTIFY_DONE).
>
> Cc: Alexander Gordeev <agord...@linux.ibm.com>
> Cc: Andrea Parri (Microsoft) <parri.and...@gmail.com>
> Cc: Ard Biesheuvel <a...@kernel.org>
> Cc: Benjamin Herrenschmidt <b...@kernel.crashing.org>
> Cc: Brian Norris <computersforpe...@gmail.com>
> Cc: Christian Borntraeger <borntrae...@linux.ibm.com>
> Cc: Christophe JAILLET <christophe.jail...@wanadoo.fr>
> Cc: David Gow <david...@google.com>
> Cc: "David S. Miller" <da...@davemloft.net>
> Cc: Dexuan Cui <de...@microsoft.com>
> Cc: Doug Berger <open...@gmail.com>
> Cc: Evan Green <evgr...@chromium.org>
> Cc: Florian Fainelli <f.faine...@gmail.com>
> Cc: Haiyang Zhang <haiya...@microsoft.com>
> Cc: Hari Bathini <hbath...@linux.ibm.com>
> Cc: Heiko Carstens <h...@linux.ibm.com>
> Cc: Julius Werner <jwer...@chromium.org>
> Cc: Justin Chen <justinpo...@gmail.com>
> Cc: "K. Y. Srinivasan" <k...@microsoft.com>
> Cc: Lee Jones <lee.jo...@linaro.org>
> Cc: Markus Mayer <mma...@broadcom.com>
> Cc: Michael Ellerman <m...@ellerman.id.au>
> Cc: Michael Kelley <mikel...@microsoft.com>
> Cc: Mihai Carabas <mihai.cara...@oracle.com>
> Cc: Nicholas Piggin <npig...@gmail.com>
> Cc: Paul Mackerras <pau...@samba.org>
> Cc: Pavel Machek <pa...@ucw.cz>
> Cc: Scott Branden <scott.bran...@broadcom.com>
> Cc: Sebastian Reichel <s...@kernel.org>
> Cc: Shile Zhang <shile.zh...@linux.alibaba.com>
> Cc: Stephen Hemminger <sthem...@microsoft.com>
> Cc: Sven Schnelle <sv...@linux.ibm.com>
> Cc: Thomas Bogendoerfer <tsbog...@alpha.franken.de>
> Cc: Tianyu Lan <tianyu....@microsoft.com>
> Cc: Vasily Gorbik <g...@linux.ibm.com>
> Cc: Wang ShaoBo <bobo.shaobow...@huawei.com>
> Cc: Wei Liu <wei....@kernel.org>
> Cc: zhenwei pi <pizhen...@bytedance.com>
> Signed-off-by: Guilherme G. Piccoli <gpicc...@igalia.com>
> ---
> arch/mips/sgi-ip22/ip22-reset.c | 2 +-
> arch/mips/sgi-ip32/ip32-reset.c | 3 +--
> arch/powerpc/kernel/setup-common.c | 2 +-
> arch/sparc/kernel/sstate.c | 3 +--
> drivers/firmware/google/gsmi.c | 4 ++--
> drivers/hv/vmbus_drv.c | 4 ++--
> drivers/leds/trigger/ledtrig-activity.c | 4 ++--
> drivers/leds/trigger/ledtrig-heartbeat.c | 4 ++--
> drivers/misc/bcm-vk/bcm_vk_dev.c | 6 +++---
> drivers/misc/pvpanic/pvpanic.c | 4 ++--
> drivers/power/reset/ltc2952-poweroff.c | 4 ++--
> drivers/s390/char/zcore.c | 5 +++--
> drivers/soc/bcm/brcmstb/pm/pm-arm.c | 2 +-
> include/linux/panic_notifier.h | 1 +
> kernel/panic.c | 4 ++++
> 15 files changed, 28 insertions(+), 24 deletions(-)
[ snip]
>
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index f37f12d48001..901b97034308 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -1614,7 +1614,7 @@ static int vmbus_bus_init(void)
> hv_kmsg_dump_register();
>
> register_die_notifier(&hyperv_die_report_block);
> - atomic_notifier_chain_register(&panic_notifier_list,
> + atomic_notifier_chain_register(&panic_hypervisor_list,
> &hyperv_panic_report_block);
> }
>
> @@ -2843,7 +2843,7 @@ static void __exit vmbus_exit(void)
> if (ms_hyperv.misc_features & HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE) {
> kmsg_dump_unregister(&hv_kmsg_dumper);
> unregister_die_notifier(&hyperv_die_report_block);
> - atomic_notifier_chain_unregister(&panic_notifier_list,
> + atomic_notifier_chain_unregister(&panic_hypervisor_list,
> &hyperv_panic_report_block);
> }
>
Using the hypervisor_list here produces a bit of a mismatch. In many cases
this notifier will do nothing, and will defer to the kmsg_dump() mechanism
to notify the hypervisor about the panic. Running the kmsg_dump()
mechanism is linked to the info_list, so I'm thinking the Hyper-V panic report
notifier should be on the info_list as well. That way the reporting behavior
is triggered at the same point in the panic path regardless of which
reporting mechanism is used.
