Received: by 2002:a05:6a10:83d0:0:0:0:0 with SMTP id o16csp75368pxh; Thu, 7 Apr 2022 14:26:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy3xep8OMD9aBlSlv2uhRWQKuaWbb/ApC+iiblif82MfLyhLCZ/UCer02BCY/4K0nV6jAF1 X-Received: by 2002:a17:90b:4b06:b0:1c9:9751:cf9b with SMTP id lx6-20020a17090b4b0600b001c99751cf9bmr18151859pjb.0.1649366806991; Thu, 07 Apr 2022 14:26:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649366806; cv=none; d=google.com; s=arc-20160816; b=wDv6ib2dsJHB7QeaUWp50XvV63eUmSoi7MFs71TkmS4+wNVC2Nm5eZKKZL6YgGmfdM dK9+ejQdx5wsZP7aSW6UE2Q9s7f7Kl7HCeNBU1CNUlD9AFCbA+DzkH1q0F01rHBV3Hz1 rXQhfc/YG3k62E51b7C6KIS+4uayLArjfDTNTndtHJG5o6ggZZktXQQTgwjPKazNSlbl lPWxCbKaaycQ8H+4V22TEC98mUsnNKDSR7fvviu8X1cHERyZJ6yPJBH6e+f2U7xjbTX8 oOsb5YBO91wDKVLj1L1oQvOqVMVYRSgTPJGBraG+LLSe6LSws/NnegdKU3XfegadlhlB ozoQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=2BKDWOjtgIXDX/Y1V4nBQcuPkNTmmYt5n1xkIPQmGJ0=; b=Tk84NPk08qT2uDKlSK+fm9iLpu6+OBUmUQqDa8F92+7oiN4Fj/urygzrvFnCon2vEm LC62McmU50GJqDWYeQOZ36oFfVMGa8Ut/yJzvqqm/eoHWwcE4Cka95l3tMLsjcxaPjQV vgu3I2dsMAGCrD+fvO/MYhwIzgXP+u1apXU4lzW0+xaUHc8+VHC9oFlr6e/9x3DNNaNh k4as5mMMM1tfRxAd4KQ4SZNl7mcbpUTalGhq2WzxXKc+WPWQeSr2bA7Dht1QPjJdLth/ CrsggWNwMDmJ64S1jWb5Wx/xf5KULvcVmg8PCb9MmCjcfeQLO6S9EPUggkKt/d7o5/xN 5bmg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux-foundation.org header.s=korg header.b=xBbKyofi; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id 76-20020a63004f000000b0039cc53ff373si3247221pga.625.2022.04.07.14.26.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Apr 2022 14:26:46 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@linux-foundation.org header.s=korg header.b=xBbKyofi; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 4BB3D31BBA6; Thu, 7 Apr 2022 13:31:25 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229902AbiDGUdS (ORCPT + 99 others); Thu, 7 Apr 2022 16:33:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34698 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229762AbiDGUdM (ORCPT ); Thu, 7 Apr 2022 16:33:12 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2D96030F9CA for ; Thu, 7 Apr 2022 13:18:12 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 9509E61EE5 for ; Thu, 7 Apr 2022 20:18:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6AA2FC385A4; Thu, 7 Apr 2022 20:18:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1649362691; bh=ri7xT8MCx8mwYgjZZIPM9V0zwZwR3Rdo4TKvPfNTfd0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=xBbKyofi0Z7kXY4nRilQftAnBHdLY0oC81M9HNli7qkV8OWhTGjAwIYx7MbeamNgc U4hlm0L+KpoOZ+kLyp6QUxBdL1unJTB0tlcYBqjkWc2FX6Y/WE1sr08kewZSq76gy5 xj4iUIe4oPSivbqKNlQRaT7k3VoH5/OayM8eL/QA= Date: Thu, 7 Apr 2022 13:18:09 -0700 From: Andrew Morton To: Nico Pache Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Rafael Aquini , Waiman Long , Baoquan He , Christoph von Recklinghausen , Don Dutile , "Herton R . Krzesinski" , David Rientjes , Michal Hocko , Andrea Arcangeli , Davidlohr Bueso , Thomas Gleixner , Peter Zijlstra , Ingo Molnar , Joel Savitz , Darren Hart Subject: Re: [PATCH v6] oom_kill.c: futex: Don't OOM reap the VMA containing the robust_list_head Message-Id: <20220407131809.f2d256541e2c039c434c0d72@linux-foundation.org> In-Reply-To: <20220407184254.3612387-1-npache@redhat.com> References: <20220407184254.3612387-1-npache@redhat.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_NONE,SPF_HELO_NONE, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 7 Apr 2022 14:42:54 -0400 Nico Pache wrote: > The pthread struct is allocated on PRIVATE|ANONYMOUS memory [1] which can > be targeted by the oom reaper. This mapping is used to store the futex > robust list head; the kernel does not keep a copy of the robust list and > instead references a userspace address to maintain the robustness during > a process death. A race can occur between exit_mm and the oom reaper that > allows the oom reaper to free the memory of the futex robust list before > the exit path has handled the futex death: > > CPU1 CPU2 > ------------------------------------------------------------------------ > page_fault > do_exit "signal" > wake_oom_reaper > oom_reaper > oom_reap_task_mm (invalidates mm) > exit_mm > exit_mm_release > futex_exit_release > futex_cleanup > exit_robust_list > get_user (EFAULT- can't access memory) > > If the get_user EFAULT's, the kernel will be unable to recover the > waiters on the robust_list, leaving userspace mutexes hung indefinitely. > > Use the robust_list address stored in the kernel to skip the VMA that holds > it, allowing a successful futex_cleanup. > > Theoretically a failure can still occur if there are locks mapped as > PRIVATE|ANON; however, the robust futexes are a best-effort approach. > This patch only strengthens that best-effort. > > The following case can still fail: > robust head (skipped) -> private lock (reaped) -> shared lock (skipped) > > Reproducer: https://gitlab.com/jsavitz/oom_futex_reproducer Should this fix be backported into -stable kernels? > --- a/include/linux/oom.h > +++ b/include/linux/oom.h > @@ -106,7 +106,8 @@ static inline vm_fault_t check_stable_address_space(struct mm_struct *mm) > return 0; > } > > -bool __oom_reap_task_mm(struct mm_struct *mm); > +bool __oom_reap_task_mm(struct mm_struct *mm, struct robust_list_head > + __user *robust_list); Should explicitly include futex.h > long oom_badness(struct task_struct *p, > unsigned long totalpages); > diff --git a/mm/mmap.c b/mm/mmap.c > index 3aa839f81e63..c14fe6f8e9a5 100644 > --- a/mm/mmap.c > +++ b/mm/mmap.c > @@ -3126,7 +3126,8 @@ void exit_mmap(struct mm_struct *mm) > * to mmu_notifier_release(mm) ensures mmu notifier callbacks in > * __oom_reap_task_mm() will not block. > */ > - (void)__oom_reap_task_mm(mm); > + (void)__oom_reap_task_mm(mm, current->robust_list); > + > set_bit(MMF_OOM_SKIP, &mm->flags); > } > > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > index 7ec38194f8e1..727cfc3bd284 100644 > --- a/mm/oom_kill.c > +++ b/mm/oom_kill.c > @@ -509,9 +509,11 @@ static DECLARE_WAIT_QUEUE_HEAD(oom_reaper_wait); > static struct task_struct *oom_reaper_list; > static DEFINE_SPINLOCK(oom_reaper_lock); > > -bool __oom_reap_task_mm(struct mm_struct *mm) > +bool __oom_reap_task_mm(struct mm_struct *mm, struct robust_list_head > + __user *robust_list) > { It's pretty sad to make such a low-level function aware of futex internals. How about making it a more general `void *skip_area'? > struct vm_area_struct *vma; > + unsigned long head = (unsigned long) robust_list; > bool ret = true; > > /* > @@ -526,6 +528,11 @@ bool __oom_reap_task_mm(struct mm_struct *mm) > if (vma->vm_flags & (VM_HUGETLB|VM_PFNMAP)) > continue; > > + if (vma->vm_start <= head && vma->vm_end > head) { This check as you have it is making assumptions about the length of the area at *robust_list and about that area's relation to the area represented by the vma. So if this is to be made more generic, we'd also need skip_area_len so we can perform a full overlap check. I dunno, maybe not worth it at this time, what do others think. But the special-casing in here is pretty painful. > + pr_info("oom_reaper: skipping vma, contains robust_list"); > + continue; > + } > + > /* > * Only anonymous pages have a good chance to be dropped > * without additional steps which we cannot afford as we > @@ -587,7 +594,7 @@ static bool oom_reap_task_mm(struct task_struct *tsk, struct mm_struct *mm) > trace_start_task_reaping(tsk->pid); > > /* failed to reap part of the address space. Try again later */ > - ret = __oom_reap_task_mm(mm); > + ret = __oom_reap_task_mm(mm, tsk->robust_list); > if (!ret) > goto out_finish; > > @@ -1190,7 +1197,8 @@ SYSCALL_DEFINE2(process_mrelease, int, pidfd, unsigned int, flags) > * Check MMF_OOM_SKIP again under mmap_read_lock protection to ensure > * possible change in exit_mmap is seen > */ > - if (!test_bit(MMF_OOM_SKIP, &mm->flags) && !__oom_reap_task_mm(mm)) > + if (!test_bit(MMF_OOM_SKIP, &mm->flags) && > + !__oom_reap_task_mm(mm, p->robust_list)) > ret = -EAGAIN; > mmap_read_unlock(mm); > > -- > 2.35.1