Commit 7f80a2fd authored by Eric W. Biederman's avatar Eric W. Biederman

exit: Stop poorly open coding do_task_dead in make_task_dead

When the kernel detects it is oops or otherwise force killing a task
while it exits the code poorly attempts to permanently stop the task
from scheduling.

I say poorly because it is possible for a task in TASK_UINTERRUPTIBLE
to be woken up.

As it makes no sense for the task to continue call do_task_dead
instead which actually does the work and permanently removes the task
from the scheduler.  Guaranteeing the task will never be woken
up again.
Signed-off-by: default avatar"Eric W. Biederman" <ebiederm@xmission.com>
parent 05ea0424
...@@ -886,8 +886,7 @@ void __noreturn make_task_dead(int signr) ...@@ -886,8 +886,7 @@ void __noreturn make_task_dead(int signr)
if (unlikely(tsk->flags & PF_EXITING)) { if (unlikely(tsk->flags & PF_EXITING)) {
pr_alert("Fixing recursive fault but reboot is needed!\n"); pr_alert("Fixing recursive fault but reboot is needed!\n");
futex_exit_recursive(tsk); futex_exit_recursive(tsk);
set_current_state(TASK_UNINTERRUPTIBLE); do_task_dead();
schedule();
} }
do_exit(signr); do_exit(signr);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment