From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751696AbbCJArP (ORCPT ); Mon, 9 Mar 2015 20:47:15 -0400 Received: from mail-ig0-f179.google.com ([209.85.213.179]:33376 "EHLO mail-ig0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750933AbbCJArN (ORCPT ); Mon, 9 Mar 2015 20:47:13 -0400 References: <20150309043051.GA13380@node.dhcp.inet.fi> From: Greg Thelen To: David Rientjes Cc: Andrew Morton , Naoya Horiguchi , Davidlohr Bueso , "Kirill A. Shutemov" , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [patch v3] mm, hugetlb: abort __get_user_pages if current has been oom killed In-reply-to: Date: Mon, 09 Mar 2015 17:47:08 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 09 2015, David Rientjes wrote: > If __get_user_pages() is faulting a significant number of hugetlb pages, > usually as the result of mmap(MAP_LOCKED), it can potentially allocate a > very large amount of memory. > > If the process has been oom killed, this will cause a lot of memory to > potentially deplete memory reserves. > > In the same way that commit 4779280d1ea4 ("mm: make get_user_pages() > interruptible") aborted for pending SIGKILLs when faulting non-hugetlb > memory, based on the premise of commit 462e00cc7151 ("oom: stop > allocating user memory if TIF_MEMDIE is set"), hugetlb page faults now > terminate when the process has been oom killed. > > Cc: Greg Thelen > Cc: Naoya Horiguchi > Cc: Davidlohr Bueso > Acked-by: "Kirill A. Shutemov" > Signed-off-by: David Rientjes Looks good. Acked-by: "Greg Thelen"