| Message ID | 20241219-hw_protection-reboot-v1-5-263a0c1df802@pengutronix.de (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | reboot: support runtime configuration of emergency hw_protection action | expand |
diff --git a/kernel/reboot.c b/kernel/reboot.c index da6c8bdeeefe627a76c7ec6e8926138ebbe3ae4e..aa6317939af41c9730ec5a74b7faf03f7c0f25a7 100644 --- a/kernel/reboot.c +++ b/kernel/reboot.c @@ -1023,7 +1023,8 @@ void __hw_protection_trigger(const char *reason, int ms_until_forced, { static atomic_t allow_proceed = ATOMIC_INIT(1); - pr_emerg("HARDWARE PROTECTION shutdown (%s)\n", reason); + pr_emerg("HARDWARE PROTECTION %s (%s)\n", + hw_protection_action_str(action), reason); /* Shutdown should be initiated only once. */ if (!atomic_dec_and_test(&allow_proceed))
It currently depends on the caller, whether we attempt a hardware protection shutdown (poweroff) or a reboot. A follow-up commit will make this partially user-configurable, so it's a good idea to have the emergency message clearly state whether the kernel is going for a reboot or a shutdown. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> --- kernel/reboot.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)