diff options
author | Eric W. Biederman <ebiederm@xmission.com> | 2021-11-22 16:33:00 +0100 |
---|---|---|
committer | Eric W. Biederman <ebiederm@xmission.com> | 2021-12-13 19:04:45 +0100 |
commit | 05ea0424f0e21c0ef9b47c89826e7c22ae137975 (patch) | |
tree | 8639eff37019d3dcf8999b5a47a905909109ef62 /kernel/futex | |
parent | exit: Add and use make_task_dead. (diff) | |
download | linux-05ea0424f0e21c0ef9b47c89826e7c22ae137975.tar.xz linux-05ea0424f0e21c0ef9b47c89826e7c22ae137975.zip |
exit: Move oops specific logic from do_exit into make_task_dead
The beginning of do_exit has become cluttered and difficult to read as
it is filled with checks to handle things that can only happen when
the kernel is operating improperly.
Now that we have a dedicated function for cleaning up a task when the
kernel is operating improperly move the checks there.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'kernel/futex')
-rw-r--r-- | kernel/futex/core.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/futex/core.c b/kernel/futex/core.c index 25d8a88b32e5..39a1522865b5 100644 --- a/kernel/futex/core.c +++ b/kernel/futex/core.c @@ -1044,7 +1044,7 @@ static void futex_cleanup(struct task_struct *tsk) * actually finished the futex cleanup. The worst case for this is that the * waiter runs through the wait loop until the state becomes visible. * - * This is called from the recursive fault handling path in do_exit(). + * This is called from the recursive fault handling path in make_task_dead(). * * This is best effort. Either the futex exit code has run already or * not. If the OWNER_DIED bit has been set on the futex then the waiter can |