From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f200.google.com (mail-pf0-f200.google.com [209.85.192.200]) by kanga.kvack.org (Postfix) with ESMTP id F07826B0069 for ; Thu, 5 Jan 2017 14:13:58 -0500 (EST) Received: by mail-pf0-f200.google.com with SMTP id y68so825056163pfb.6 for ; Thu, 05 Jan 2017 11:13:58 -0800 (PST) Received: from mga04.intel.com (mga04.intel.com. [192.55.52.120]) by mx.google.com with ESMTPS id y186si55546451pgd.113.2017.01.05.11.13.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Jan 2017 11:13:58 -0800 (PST) Subject: Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR References: <20161227015413.187403-1-kirill.shutemov@linux.intel.com> <20161227015413.187403-30-kirill.shutemov@linux.intel.com> From: Dave Hansen Message-ID: <5a3dcc25-b264-37c7-c090-09981b23940d@intel.com> Date: Thu, 5 Jan 2017 11:13:57 -0800 MIME-Version: 1.0 In-Reply-To: <20161227015413.187403-30-kirill.shutemov@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: "Kirill A. Shutemov" , Linus Torvalds , Andrew Morton , x86@kernel.org, Thomas Gleixner , Ingo Molnar , Arnd Bergmann , "H. Peter Anvin" Cc: Andi Kleen , Andy Lutomirski , linux-arch@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org On 12/26/2016 05:54 PM, Kirill A. Shutemov wrote: > MM would use min(RLIMIT_VADDR, TASK_SIZE) as upper limit of virtual > address available to map by userspace. What happens to existing mappings above the limit when this upper limit is dropped? Similarly, why do we do with an application running with something incompatible with the larger address space that tries to raise the limit? Say, legacy MPX. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org