kdump-error-handler.service: Remove ExecStopPost
Currently "systemctl --fail --no-block default" will be executed on kdump-error-handler exit due to the config. This may makes systemd try to isolate to the default target again. The execute chain will be like: initrd.target -> kdump.sh (failed) -> kdump-error-handler.service -> failure_action -> final_action -> ExecStopPost (go to initrd.target again) Currently, reboot/shutdown/halt is called by either by executing failure_action or final_action. So the loop will be stopped. However nont of the reboot/shutdown/halt call is blocking so it might lead to race issue. Just drop the ExecStopPost to fix this potential issue. Signed-off-by: Kairui Song <kasong@redhat.com> Acked-by: Pingfan Liu <piliu@redhat.com> Tested-by: HATAYAMA Daisuke <d.hatayama@fujitsu.com>
This commit is contained in:
parent
f13eab60cb
commit
d13fd38df4
@ -21,7 +21,6 @@ Environment=DRACUT_SYSTEMD=1
|
|||||||
Environment=NEWROOT=/sysroot
|
Environment=NEWROOT=/sysroot
|
||||||
WorkingDirectory=/
|
WorkingDirectory=/
|
||||||
ExecStart=/bin/kdump-error-handler.sh
|
ExecStart=/bin/kdump-error-handler.sh
|
||||||
ExecStopPost=-/usr/bin/systemctl --fail --no-block default
|
|
||||||
Type=oneshot
|
Type=oneshot
|
||||||
StandardInput=tty-force
|
StandardInput=tty-force
|
||||||
StandardOutput=inherit
|
StandardOutput=inherit
|
||||||
|
Loading…
Reference in New Issue
Block a user