Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp95775imm; Thu, 21 Jun 2018 14:36:24 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJukoAA4H3mvcidhGb3jgDKZ2N1y25VoeQ9pU5PNsdnxtbfOPM1IZ55GoA4OJgyERS26P2p X-Received: by 2002:a17:902:201:: with SMTP id 1-v6mr24911128plc.310.1529616984729; Thu, 21 Jun 2018 14:36:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529616984; cv=none; d=google.com; s=arc-20160816; b=Iu3E1FkK8UqLRWWSeASijBtJMY8cbD+aDt7BGbSGwIWZf/knUXa6tEEDbWfo4mv/MS tjmfLi7YwM71qvBPVt/7ZKf7h+r5+IG20/it7m+K7oupccOitog8fVirDYXnBqny7bzC 2XYKdzCZY4G4f2Jq3nlapl/QTKwKzFaTRgl5mgI0eq9ET002MfthpwYjF+Gf4rcy5845 4UFRM/lysxc4J94DwMOwYbZdsOo4mJikF1prsVNtJbzg4/Rquki42YwKVeTE+UdFe/f9 uSejCts1VVNQ5hYrZg86wRglNnB0IzRPlrzSdsTVP57/jeivxPMjdeJ9Ok8OwNEV+9p0 DRhg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :subject:cc:to:from:date:dkim-signature:arc-authentication-results; bh=nFJLrEtu1WovBMY8/Be58xo4QJT4mOCpcjjB66seHVQ=; b=c+mC2+SUluJAgmEQaRRtRZVSygEeOA/Ql3srLjconu3i2wbAr+0Ejp0fA575LyA7Qr adN/qJ8Ko/iGpyHczCOtcOGnwROiEXpnwmaDaTf320gbrMonXdecNLZ6snQbw1eigkLt eF9REE7wGbCKTIk7ah/vZMYk4Db/ICXz67fUGo5IGrWWiNMnSYphJVYm3xbT5GfB2D9y iSJXnCwq7Q5czKAmRh4h5s0sGrdsSrJFH6EUgx2kfuyE82GUoLaXNRryZlppJw0LypId lyM6u9b0SoJiqgFkZMNhZO+GQoA2jDWpObRjbAZ/EoXOyQf3Mwn8UlAEZpKuTwMwqmb7 WNag== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=psyBV8v9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p12-v6si6547253pll.142.2018.06.21.14.36.10; Thu, 21 Jun 2018 14:36:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=psyBV8v9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933908AbeFUVf0 (ORCPT + 99 others); Thu, 21 Jun 2018 17:35:26 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:39517 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933670AbeFUVfW (ORCPT ); Thu, 21 Jun 2018 17:35:22 -0400 Received: by mail-pf0-f196.google.com with SMTP id r11-v6so2143377pfl.6 for ; Thu, 21 Jun 2018 14:35:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:user-agent:mime-version; bh=nFJLrEtu1WovBMY8/Be58xo4QJT4mOCpcjjB66seHVQ=; b=psyBV8v9LjA/OGtl2fSO8kRNy/R+DPeAUhRac27sRLxUtUsXVOkaFh1JbB3Mbavd8n IzNJCNqDuxpz0COY/v4ZE1uo/nr/FtbmHFdrZIEfX7Oe4qEQdTYbdN9jVXVB7qqbUDu1 1YyD3O4qt5bMsoN3c0jahXIEgk05bzbbMm51uq7I2Wg5J+YAcju2g6HbYTXWSgDb5Exd M9FRPlWnUdB69gTKTXRA2qfUlDNMBiQVCtiL4zB7ZraC1e3LWMYp69HgAItEUb5Qdc8m MTy2m04Pywuh1jookyLd+Fv218RWDAPJhbuZRY/keNy/0smJ87xCA+3OIb5a+xLGkABu ixJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:user-agent :mime-version; bh=nFJLrEtu1WovBMY8/Be58xo4QJT4mOCpcjjB66seHVQ=; b=VbC8RfZkxLF226X9k9uMO/PAMnlx8rFmUoD444SbFCrsGmZdR3dAawsXN72O7yLX1E JId6fbx8UJ7DyEthG4H3DWX9aTmSEjCNKPXet6k5DRpSeGtJ5lcE5KPfGf2k2blnA9TX FvK95/V1ahegkExjbJOc8zUPV5d1i72lllQavNDiYSaVk+qTkvNllWs9gEkjreB+Sn7h UsB9nrJh3ktLHGwCuE+5kRGh0+K9LZ8Ewf5p85cJfCmzm3akOkVGXmMhXlv4A8pXS608 uIkCSGlZlXyYGRq6ON5D4+HDAJHAT9HBbznZ0Gw6kId5nMlBlvcBG+gihGK/GgyAaQd5 IuXg== X-Gm-Message-State: APt69E3zEMwQOiigQhYUDKQWKfHuezHnO7TxaFhlEu/jgXQBJfriif9C LhtJdMXp2dqnD42MvObRQv0mUA== X-Received: by 2002:a62:418b:: with SMTP id g11-v6mr29143714pfd.51.1529616921415; Thu, 21 Jun 2018 14:35:21 -0700 (PDT) Received: from [2620:15c:17:3:3a5:23a7:5e32:4598] ([2620:15c:17:3:3a5:23a7:5e32:4598]) by smtp.gmail.com with ESMTPSA id l15-v6sm13096743pfg.88.2018.06.21.14.35.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 21 Jun 2018 14:35:20 -0700 (PDT) Date: Thu, 21 Jun 2018 14:35:20 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Andrew Morton cc: kbuild test robot , Michal Hocko , Tetsuo Handa , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: [patch v3] mm, oom: fix unnecessary killing of additional processes Message-ID: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The oom reaper ensures forward progress by setting MMF_OOM_SKIP itself if it cannot reap an mm. This can happen for a variety of reasons, including: - the inability to grab mm->mmap_sem in a sufficient amount of time, - when the mm has blockable mmu notifiers that could cause the oom reaper to stall indefinitely, but we can also add a third when the oom reaper can "reap" an mm but doing so is unlikely to free any amount of memory: - when the mm's memory is mostly mlocked. When all memory is mlocked, the oom reaper will not be able to free any substantial amount of memory. It sets MMF_OOM_SKIP before the victim can unmap and free its memory in exit_mmap() and subsequent oom victims are chosen unnecessarily. This is trivial to reproduce if all eligible processes on the system have mlocked their memory: the oom killer calls panic() even though forward progress can be made. This is the same issue where the exit path sets MMF_OOM_SKIP before unmapping memory and additional processes can be chosen unnecessarily because the oom killer is racing with exit_mmap() and is separate from the oom reaper setting MMF_OOM_SKIP prematurely. We can't simply defer setting MMF_OOM_SKIP, however, because if there is a true oom livelock in progress, it never gets set and no additional killing is possible. To fix this, this patch introduces a per-mm reaping period, which is configurable through the new oom_free_timeout_ms file in debugfs and defaults to one second to match the current heuristics. This support requires that the oom reaper's list becomes a proper linked list so that other mm's may be reaped while waiting for an mm's timeout to expire. This replaces the current timeouts in the oom reaper: (1) when trying to grab mm->mmap_sem 10 times in a row with HZ/10 sleeps in between and (2) a HZ sleep if there are blockable mmu notifiers. It extends it with timeout to allow an oom victim to reach exit_mmap() before choosing additional processes unnecessarily. The exit path will now set MMF_OOM_SKIP only after all memory has been freed, so additional oom killing is justified, and rely on MMF_UNSTABLE to determine when it can race with the oom reaper. The oom reaper will now set MMF_OOM_SKIP only after the reap timeout has lapsed because it can no longer guarantee forward progress. Since the default oom_free_timeout_ms is one second, the same as current heuristics, there should be no functional change with this patch for users who do not tune it to be longer other than MMF_OOM_SKIP is set by exit_mmap() after free_pgtables(), which is the preferred behavior. The reaping timeout can intentionally be set for a substantial amount of time, such as 10s, since oom livelock is a very rare occurrence and it's better to optimize for preventing additional (unnecessary) oom killing than a scenario that is much more unlikely. Signed-off-by: David Rientjes --- v3: - oom_free_timeout_ms is now static per kbuild test robot v2: - configurable timeout period through debugfs - change mm->reap_timeout to mm->oom_free_expire and add more descriptive comment per akpm - add comment to describe task->oom_reap_list locking based on oom_reaper_lock per akpm - rework the exit_mmap() comment and split into two parts to be more descriptive about the locking and the issue with the oom reaper racing with munlock_vma_pages_all() per akpm --- include/linux/mm_types.h | 7 ++ include/linux/sched.h | 3 +- kernel/fork.c | 3 + mm/mmap.c | 26 +++++--- mm/oom_kill.c | 140 +++++++++++++++++++++++++-------------- 5 files changed, 119 insertions(+), 60 deletions(-) diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h --- a/include/linux/mm_types.h +++ b/include/linux/mm_types.h @@ -449,6 +449,13 @@ struct mm_struct { #ifdef CONFIG_MMU_NOTIFIER struct mmu_notifier_mm *mmu_notifier_mm; #endif +#ifdef CONFIG_MMU + /* + * When to give up on memory freeing from this mm after its + * threads have been oom killed, in jiffies. + */ + unsigned long oom_free_expire; +#endif #if defined(CONFIG_TRANSPARENT_HUGEPAGE) && !USE_SPLIT_PMD_PTLOCKS pgtable_t pmd_huge_pte; /* protected by page_table_lock */ #endif diff --git a/include/linux/sched.h b/include/linux/sched.h --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -1163,7 +1163,8 @@ struct task_struct { #endif int pagefault_disabled; #ifdef CONFIG_MMU - struct task_struct *oom_reaper_list; + /* OOM victim queue for oom reaper, protected by oom_reaper_lock */ + struct list_head oom_reap_list; #endif #ifdef CONFIG_VMAP_STACK struct vm_struct *stack_vm_area; diff --git a/kernel/fork.c b/kernel/fork.c --- a/kernel/fork.c +++ b/kernel/fork.c @@ -842,6 +842,9 @@ static struct task_struct *dup_task_struct(struct task_struct *orig, int node) #ifdef CONFIG_FAULT_INJECTION tsk->fail_nth = 0; #endif +#ifdef CONFIG_MMU + INIT_LIST_HEAD(&tsk->oom_reap_list); +#endif return tsk; diff --git a/mm/mmap.c b/mm/mmap.c --- a/mm/mmap.c +++ b/mm/mmap.c @@ -3059,25 +3059,28 @@ void exit_mmap(struct mm_struct *mm) if (unlikely(mm_is_oom_victim(mm))) { /* * Manually reap the mm to free as much memory as possible. - * Then, as the oom reaper does, set MMF_OOM_SKIP to disregard - * this mm from further consideration. Taking mm->mmap_sem for - * write after setting MMF_OOM_SKIP will guarantee that the oom - * reaper will not run on this mm again after mmap_sem is - * dropped. - * * Nothing can be holding mm->mmap_sem here and the above call * to mmu_notifier_release(mm) ensures mmu notifier callbacks in * __oom_reap_task_mm() will not block. - * - * This needs to be done before calling munlock_vma_pages_all(), - * which clears VM_LOCKED, otherwise the oom reaper cannot - * reliably test it. */ mutex_lock(&oom_lock); __oom_reap_task_mm(mm); mutex_unlock(&oom_lock); - set_bit(MMF_OOM_SKIP, &mm->flags); + /* + * Now, set MMF_UNSTABLE to avoid racing with the oom reaper. + * This needs to be done before calling munlock_vma_pages_all(), + * which clears VM_LOCKED, otherwise the oom reaper cannot + * reliably test for it. If the oom reaper races with + * munlock_vma_pages_all(), this can result in a kernel oops if + * a pmd is zapped, for example, after follow_page_mask() has + * checked pmd_none(). + * + * Taking mm->mmap_sem for write after setting MMF_UNSTABLE will + * guarantee that the oom reaper will not run on this mm again + * after mmap_sem is dropped. + */ + set_bit(MMF_UNSTABLE, &mm->flags); down_write(&mm->mmap_sem); up_write(&mm->mmap_sem); } @@ -3105,6 +3108,7 @@ void exit_mmap(struct mm_struct *mm) unmap_vmas(&tlb, vma, 0, -1); free_pgtables(&tlb, vma, FIRST_USER_ADDRESS, USER_PGTABLES_CEILING); tlb_finish_mmu(&tlb, 0, -1); + set_bit(MMF_OOM_SKIP, &mm->flags); /* * Walk the list again, actually closing and freeing it, diff --git a/mm/oom_kill.c b/mm/oom_kill.c --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -41,6 +41,7 @@ #include #include #include +#include #include #include "internal.h" @@ -476,7 +477,7 @@ bool process_shares_mm(struct task_struct *p, struct mm_struct *mm) */ static struct task_struct *oom_reaper_th; static DECLARE_WAIT_QUEUE_HEAD(oom_reaper_wait); -static struct task_struct *oom_reaper_list; +static LIST_HEAD(oom_reaper_list); static DEFINE_SPINLOCK(oom_reaper_lock); void __oom_reap_task_mm(struct mm_struct *mm) @@ -519,10 +520,8 @@ void __oom_reap_task_mm(struct mm_struct *mm) } } -static bool oom_reap_task_mm(struct task_struct *tsk, struct mm_struct *mm) +static void oom_reap_task_mm(struct task_struct *tsk, struct mm_struct *mm) { - bool ret = true; - /* * We have to make sure to not race with the victim exit path * and cause premature new oom victim selection: @@ -540,9 +539,8 @@ static bool oom_reap_task_mm(struct task_struct *tsk, struct mm_struct *mm) mutex_lock(&oom_lock); if (!down_read_trylock(&mm->mmap_sem)) { - ret = false; trace_skip_task_reaping(tsk->pid); - goto unlock_oom; + goto out_oom; } /* @@ -551,69 +549,81 @@ static bool oom_reap_task_mm(struct task_struct *tsk, struct mm_struct *mm) * TODO: we really want to get rid of this ugly hack and make sure that * notifiers cannot block for unbounded amount of time */ - if (mm_has_blockable_invalidate_notifiers(mm)) { - up_read(&mm->mmap_sem); - schedule_timeout_idle(HZ); - goto unlock_oom; - } + if (mm_has_blockable_invalidate_notifiers(mm)) + goto out_mm; /* - * MMF_OOM_SKIP is set by exit_mmap when the OOM reaper can't - * work on the mm anymore. The check for MMF_OOM_SKIP must run + * MMF_UNSTABLE is set by exit_mmap when the OOM reaper can't + * work on the mm anymore. The check for MMF_UNSTABLE must run * under mmap_sem for reading because it serializes against the * down_write();up_write() cycle in exit_mmap(). */ - if (test_bit(MMF_OOM_SKIP, &mm->flags)) { - up_read(&mm->mmap_sem); + if (test_bit(MMF_UNSTABLE, &mm->flags)) { trace_skip_task_reaping(tsk->pid); - goto unlock_oom; + goto out_mm; } trace_start_task_reaping(tsk->pid); - __oom_reap_task_mm(mm); + trace_finish_task_reaping(tsk->pid); pr_info("oom_reaper: reaped process %d (%s), now anon-rss:%lukB, file-rss:%lukB, shmem-rss:%lukB\n", task_pid_nr(tsk), tsk->comm, K(get_mm_counter(mm, MM_ANONPAGES)), K(get_mm_counter(mm, MM_FILEPAGES)), K(get_mm_counter(mm, MM_SHMEMPAGES))); +out_mm: up_read(&mm->mmap_sem); - - trace_finish_task_reaping(tsk->pid); -unlock_oom: +out_oom: mutex_unlock(&oom_lock); - return ret; } -#define MAX_OOM_REAP_RETRIES 10 static void oom_reap_task(struct task_struct *tsk) { - int attempts = 0; struct mm_struct *mm = tsk->signal->oom_mm; - /* Retry the down_read_trylock(mmap_sem) a few times */ - while (attempts++ < MAX_OOM_REAP_RETRIES && !oom_reap_task_mm(tsk, mm)) - schedule_timeout_idle(HZ/10); + /* + * If this mm has either been fully unmapped, or the oom reaper has + * given up on it, nothing left to do except drop the refcount. + */ + if (test_bit(MMF_OOM_SKIP, &mm->flags)) + goto drop; - if (attempts <= MAX_OOM_REAP_RETRIES || - test_bit(MMF_OOM_SKIP, &mm->flags)) - goto done; + /* + * If this mm has already been reaped, doing so again will not likely + * free additional memory. + */ + if (!test_bit(MMF_UNSTABLE, &mm->flags)) + oom_reap_task_mm(tsk, mm); - pr_info("oom_reaper: unable to reap pid:%d (%s)\n", - task_pid_nr(tsk), tsk->comm); - debug_show_all_locks(); + if (time_after_eq(jiffies, mm->oom_free_expire)) { + if (!test_bit(MMF_OOM_SKIP, &mm->flags)) { + pr_info("oom_reaper: unable to reap pid:%d (%s)\n", + task_pid_nr(tsk), tsk->comm); + debug_show_all_locks(); -done: - tsk->oom_reaper_list = NULL; + /* + * Reaping has failed for the timeout period, so give up + * and allow additional processes to be oom killed. + */ + set_bit(MMF_OOM_SKIP, &mm->flags); + } + goto drop; + } - /* - * Hide this mm from OOM killer because it has been either reaped or - * somebody can't call up_write(mmap_sem). - */ - set_bit(MMF_OOM_SKIP, &mm->flags); + if (test_bit(MMF_OOM_SKIP, &mm->flags)) + goto drop; + + /* Enqueue to be reaped again */ + spin_lock(&oom_reaper_lock); + list_add_tail(&tsk->oom_reap_list, &oom_reaper_list); + spin_unlock(&oom_reaper_lock); - /* Drop a reference taken by wake_oom_reaper */ + schedule_timeout_idle(HZ/10); + return; + +drop: + /* Drop the reference taken by wake_oom_reaper */ put_task_struct(tsk); } @@ -622,11 +632,13 @@ static int oom_reaper(void *unused) while (true) { struct task_struct *tsk = NULL; - wait_event_freezable(oom_reaper_wait, oom_reaper_list != NULL); + wait_event_freezable(oom_reaper_wait, + !list_empty(&oom_reaper_list)); spin_lock(&oom_reaper_lock); - if (oom_reaper_list != NULL) { - tsk = oom_reaper_list; - oom_reaper_list = tsk->oom_reaper_list; + if (!list_empty(&oom_reaper_list)) { + tsk = list_entry(oom_reaper_list.next, + struct task_struct, oom_reap_list); + list_del(&tsk->oom_reap_list); } spin_unlock(&oom_reaper_lock); @@ -637,25 +649,57 @@ static int oom_reaper(void *unused) return 0; } +/* + * Millisecs to wait for an oom mm to free memory before selecting another + * victim. + */ +static u64 oom_free_timeout_ms = 1000; static void wake_oom_reaper(struct task_struct *tsk) { - /* tsk is already queued? */ - if (tsk == oom_reaper_list || tsk->oom_reaper_list) + /* + * Set the reap timeout; if it's already set, the mm is enqueued and + * this tsk can be ignored. + */ + if (cmpxchg(&tsk->signal->oom_mm->oom_free_expire, 0UL, + jiffies + msecs_to_jiffies(oom_free_timeout_ms))) return; get_task_struct(tsk); spin_lock(&oom_reaper_lock); - tsk->oom_reaper_list = oom_reaper_list; - oom_reaper_list = tsk; + list_add(&tsk->oom_reap_list, &oom_reaper_list); spin_unlock(&oom_reaper_lock); trace_wake_reaper(tsk->pid); wake_up(&oom_reaper_wait); } +#ifdef CONFIG_DEBUG_FS +static int oom_free_timeout_ms_read(void *data, u64 *val) +{ + *val = oom_free_timeout_ms; + return 0; +} + +static int oom_free_timeout_ms_write(void *data, u64 val) +{ + if (val > 60 * 1000) + return -EINVAL; + + oom_free_timeout_ms = val; + return 0; +} +DEFINE_SIMPLE_ATTRIBUTE(oom_free_timeout_ms_fops, oom_free_timeout_ms_read, + oom_free_timeout_ms_write, "%llu\n"); +#endif /* CONFIG_DEBUG_FS */ + static int __init oom_init(void) { oom_reaper_th = kthread_run(oom_reaper, NULL, "oom_reaper"); +#ifdef CONFIG_DEBUG_FS + if (!IS_ERR(oom_reaper_th)) + debugfs_create_file("oom_free_timeout_ms", 0200, NULL, NULL, + &oom_free_timeout_ms_fops); +#endif return 0; } subsys_initcall(oom_init)