From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f199.google.com (mail-wr0-f199.google.com [209.85.128.199]) by kanga.kvack.org (Postfix) with ESMTP id 1A1676B0033 for ; Wed, 15 Nov 2017 06:27:06 -0500 (EST) Received: by mail-wr0-f199.google.com with SMTP id s8so852120wrc.16 for ; Wed, 15 Nov 2017 03:27:06 -0800 (PST) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id b13sor12168767edk.55.2017.11.15.03.27.04 for (Google Transport Security); Wed, 15 Nov 2017 03:27:04 -0800 (PST) Date: Wed, 15 Nov 2017 14:27:02 +0300 From: "Kirill A. Shutemov" Subject: Re: [PATCHv2 1/2] x86/mm: Do not allow non-MAP_FIXED mapping across DEFAULT_MAP_WINDOW border Message-ID: <20171115112702.e2m66wons37imtcj@node.shutemov.name> References: <20171114134322.40321-1-kirill.shutemov@linux.intel.com> <20171114202102.crpgiwgv2lu5aboq@node.shutemov.name> <20171114222718.76w4lmclf6wasbl3@node.shutemov.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Thomas Gleixner Cc: "Kirill A. Shutemov" , Ingo Molnar , x86@kernel.org, "H. Peter Anvin" , Linus Torvalds , Andy Lutomirski , Nicholas Piggin , linux-mm@kvack.org, linux-kernel@vger.kernel.org On Wed, Nov 15, 2017 at 12:00:46AM +0100, Thomas Gleixner wrote: > On Wed, 15 Nov 2017, Kirill A. Shutemov wrote: > > On Tue, Nov 14, 2017 at 09:54:52PM +0100, Thomas Gleixner wrote: > > > On Tue, 14 Nov 2017, Kirill A. Shutemov wrote: > > > > > > > On Tue, Nov 14, 2017 at 05:01:50PM +0100, Thomas Gleixner wrote: > > > > > @@ -198,11 +199,14 @@ arch_get_unmapped_area_topdown(struct fi > > > > > /* requesting a specific address */ > > > > > if (addr) { > > > > > addr = PAGE_ALIGN(addr); > > > > > + if (!mmap_address_hint_valid(addr, len)) > > > > > + goto get_unmapped_area; > > > > > + > > > > > > > > Here and in hugetlb_get_unmapped_area(), we should align the addr after > > > > the check, not before. Otherwise the alignment itself can bring us over > > > > the borderline as we align up. > > > > > > Hmm, then I wonder whether the next check against vm_start_gap() which > > > checks against the aligned address is correct: > > > > > > addr = PAGE_ALIGN(addr); > > > vma = find_vma(mm, addr); > > > > > > if (end - len >= addr && > > > (!vma || addr + len <= vm_start_gap(vma))) > > > return addr; > > > > I think the check is correct. The check is against resulting addresses > > that end up in vm_start/vm_end. In our case we want to figure out what > > user asked for. > > Well, but then checking just against the user supplied addr is only half of > the story. > > addr = boundary - PAGE_SIZE - PAGE_SIZE / 2; > len = PAGE_SIZE - PAGE_SIZE / 2; > > That fits, but then after alignment we end up with > > addr = boudary - PAGE_SIZE; > > and due to len > PAGE_SIZE this will result in a mapping which crosses the > boundary, right? So checking against the PAGE_ALIGN(addr) should be the > right thing to do. IIUC, this is only the case if 'len' is not aligned, right? >>From what I see we expect caller to align it (and mm/mmap.c does this, I haven't checked other callers). And hugetlb would actively reject non-aligned len. I *think* we should be fine with checking unaligned 'addr'. -- Kirill A. Shutemov -- 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