aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/fs/exec.c
diff options
context:
space:
mode:
authorDongmin Lee <ldmldm05@gmail.com>2023-11-04 20:33:20 +0900
committerAndrew Morton <akpm@linux-foundation.org>2023-12-10 17:21:25 -0800
commita9a1d6ad668f2ea0b5a77d0c4c7a41446d0801a8 (patch)
tree2bf6d83a2a49250ca19d2d996034b9329191a5cb /fs/exec.c
parentMerge branch 'master' into mm-hotfixes-stable (diff)
downloadwireguard-linux-a9a1d6ad668f2ea0b5a77d0c4c7a41446d0801a8.tar.xz
wireguard-linux-a9a1d6ad668f2ea0b5a77d0c4c7a41446d0801a8.zip
kernel/reboot: explicitly notify if halt occurred instead of power off
When kernel_can_power_off() returns false, and reboot has called with LINUX_REBOOT_CMD_POWER_OFF, kernel_halt() will be initiated instead of actual power off function. However, in this situation, Kernel never explicitly notifies user that system halted instead of requested power off. Since halt and power off perform different behavior, and user initiated reboot call with power off command, not halt, This could be unintended behavior to user, like this: ~ # poweroff -f [ 3.581482] reboot: System halted Therefore, this explicitly notifies user that poweroff is not available, and halting has been occured as an alternative behavior instead: ~ # poweroff -f [ 4.123668] reboot: Power off not available: System halted instead [akpm@linux-foundation.org: tweak comment text] Link: https://lkml.kernel.org/r/20231104113320.72440-1-ldmldm05@gmail.com Signed-off-by: Dongmin Lee <ldmldm05@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'fs/exec.c')
0 files changed, 0 insertions, 0 deletions