Re: [PATCH 1/8] mm,oom_reaper: Remove pointless kthread_run() failure check.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon 04-07-16 06:53:49, Tetsuo Handa wrote:
[...]
> >From 977b0f4368a7ca07af7e519aa8795e7b2ee653d0 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
> Date: Mon, 4 Jul 2016 06:40:05 +0900
> Subject: [PATCH 1/8] mm,oom_reaper: Don't boot without OOM reaper kernel thread.
> 
> We are trying to prove that OOM livelock is impossible for CONFIG_MMU=y
> kernels (as long as OOM killer is invoked) because the OOM reaper always
> gives feedback to the OOM killer. Therefore, preserving code which
> continues without OOM reaper no longer makes sense.
> 
> Since oom_init() is called before OOM-killable userspace processes are
> started, the system will panic if out_of_memory() is called before
> oom_init() returns. Therefore, oom_reaper_th == NULL check in
> wake_oom_reaper() is pointless.
> 
> If kthread_run() in oom_init() fails due to reasons other than
> out_of_memory(), userspace processes won't be able to start as well.
> Therefore, trying to continue with error message is also pointless.
> But in case something unexpected occurred, let's explicitly add
> BUG_ON() check.

I have said that earlier already. The oom_reaper is not crucial for the
standard system operation. Panicing on this failure seems like an over
reaction. It is true that the system might panic just right after for
other reasons but that is not the reason to panic here.

> Signed-off-by: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>

I am not going to ack nor nak this patch because it will have no
practical effect.

> ---
>  mm/oom_kill.c | 13 +++----------
>  1 file changed, 3 insertions(+), 10 deletions(-)
> 
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 7d0a275..079ce96 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -447,7 +447,6 @@ bool process_shares_mm(struct task_struct *p, struct mm_struct *mm)
>   * OOM Reaper kernel thread which tries to reap the memory used by the OOM
>   * victim (if that is possible) to help the OOM killer to move on.
>   */
> -static struct task_struct *oom_reaper_th;
>  static DECLARE_WAIT_QUEUE_HEAD(oom_reaper_wait);
>  static struct task_struct *oom_reaper_list;
>  static DEFINE_SPINLOCK(oom_reaper_lock);
> @@ -629,9 +628,6 @@ static int oom_reaper(void *unused)
>  
>  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;
> @@ -647,12 +643,9 @@ 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;
> -	}
> +	struct task_struct *p = kthread_run(oom_reaper, NULL, "oom_reaper");
> +
> +	BUG_ON(IS_ERR(p));
>  	return 0;
>  }
>  subsys_initcall(oom_init)
> -- 
> 1.8.3.1

-- 
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>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]