From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits Date: Thu, 18 May 2017 13:43:59 +0200 Message-ID: <20170518114359.GB25471@dhcp22.suse.cz> References: <20170515121218.27610-1-kirill.shutemov@linux.intel.com> <20170515121218.27610-10-kirill.shutemov@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20170515121218.27610-10-kirill.shutemov@linux.intel.com> Sender: owner-linux-mm@kvack.org To: "Kirill A. Shutemov" Cc: x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andi Kleen , Dave Hansen , Andy Lutomirski , Dan Williams , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org List-Id: linux-api@vger.kernel.org On Mon 15-05-17 15:12:18, Kirill A. Shutemov wrote: [...] > @@ -195,6 +207,16 @@ arch_get_unmapped_area_topdown(struct file *filp, const unsigned long addr0, > info.length = len; > info.low_limit = PAGE_SIZE; > info.high_limit = get_mmap_base(0); > + > + /* > + * If hint address is above DEFAULT_MAP_WINDOW, look for unmapped area > + * in the full address space. > + * > + * !in_compat_syscall() check to avoid high addresses for x32. > + */ > + if (addr > DEFAULT_MAP_WINDOW && !in_compat_syscall()) > + info.high_limit += TASK_SIZE_MAX - DEFAULT_MAP_WINDOW; > + > info.align_mask = 0; > info.align_offset = pgoff << PAGE_SHIFT; > if (filp) { I have two questions/concerns here. The above assumes that any address above 1<<47 will use the _whole_ address space. Is this what we want? What if somebody does mmap(1<<52, ...) because he wants to (ab)use 53+ bits for some other purpose? Shouldn't we cap the high_limit by the given address? Another thing would be that /* requesting a specific address */ if (addr) { addr = PAGE_ALIGN(addr); vma = find_vma(mm, addr); if (TASK_SIZE - len >= addr && (!vma || addr + len <= vma->vm_start)) return addr; } would fail for mmap(-1UL, ...) which is good because we do want to fallback to vm_unmapped_area and have randomized address which is ensured by your info.high_limit += ... but that wouldn't work for mmap(1<47. So the first such mapping won't be randomized while others will be. This is quite unexpected I would say. So it should be documented at least or maybe we want to skip the above shortcut for addr > DEFAULT_MAP_WINDOW altogether. The patch looks sensible other than that. -- Michal Hocko SUSE Labs -- 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