Thank you that you have CCed me (as an author of the code)
On Wed 08-11-17 19:43:20, Tetsuo Handa wrote:
> Since oom_init() is called before userspace processes start, memory
> allocation failure for creating the OOM reaper kernel thread will let
> the OOM killer call panic() rather than wake up the OOM reaper.
Which is what I've tried to actually point out back then IIRC but you
have insisted hard so I've added the change to make a forward progress
on the whole work. The check is not harmful because this is not a
fast path but as you say we are likely to panic anyway.
> Signed-off-by: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
Acked-by: Michal Hocko <mhocko@xxxxxxxx>
> ---
> mm/oom_kill.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 8dd0e08..85eced9 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -641,9 +641,6 @@ static int oom_reaper(void *unused)
>
> static void wake_oom_reaper(struct task_struct *tsk)
> {
> - if (!oom_reaper_th)
> - return;
> -
> /* tsk is already queued? */
> if (tsk == oom_reaper_list || tsk->oom_reaper_list)
> return;
> @@ -661,11 +658,6 @@ static void wake_oom_reaper(struct task_struct *tsk)
> static int __init oom_init(void)
> {
> oom_reaper_th = kthread_run(oom_reaper, NULL, "oom_reaper");
> - if (IS_ERR(oom_reaper_th)) {
> - pr_err("Unable to start OOM reaper %ld. Continuing regardless\n",
> - PTR_ERR(oom_reaper_th));
> - oom_reaper_th = NULL;
> - }
> return 0;
> }
> subsys_initcall(oom_init)
> --
> 1.8.3.1
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@xxxxxxxxx. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
