Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1681658

[PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes in the stack

Path csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod
From Michal Hocko <mhocko@kernel.org>
Newsgroups linux.kernel
Subject [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes in the stack
Date Wed, 05 Jul 2017 19:00:01 +0200
Message-ID <tZVOF-nA-3@gated-at.bofh.it> (permalink)
X-Original-To Linus Torvalds <torvalds@linux-foundation.org>, Andrew Morton <akpm@linux-foundation.org>
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=OayBIbReF3ywvH+9syYdcriXvv2hb+yXdfeptUsfjco=; b=GzUUA75KX7my+fMODjajTR5OQiUaTrWxnVC4e4qRXpL1d3qPUrXAT1Wbgw5h1Yl9Dw tKPffEgtTdz6IYf86XI67DdZkoWSjKMHVstGL2ZGjDxbkTq7/e3IHVfVt3KgQqq1iDyO jq5kl4TyCyriHsMyB8HbME8chgcLoz8HRhheYNN/6zsJdvnCbrJgarqvpgiUc+9a+scG PpTkDfkPAhHPVmB21AmVjT5TRIrYlsz0QqhQjXvGBwLZ7kRtNgzD1rkPqfOaS3NjarhQ rOKR5lkZH+behMpPK2Vl8GgBUg3f/5kO5fY4BwhvjQRb2znPaxLxxR6idi0i07VFJ47/ ktYQ==
X-Gm-Message-State AIVw1135aTets+Z2m8pNuiq6Ql6WI127vMRxyaYQyqYIiwj5L/bZFbl0 md5Tw0AMrJLZ/w==
X-Received by 10.28.15.8 with SMTP id 8mr7479240wmp.80.1499273774694; Wed, 05 Jul 2017 09:56:14 -0700 (PDT)
X-Mailer git-send-email 2.11.0
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 57
Organization linux.* mail to news gateway
X-Original-Cc Vlastimil Babka <vbabka@suse.cz>, Ben Hutchings <ben@decadent.org.uk>, Willy Tarreau <w@1wt.eu>, Oleg Nesterov <oleg@redhat.com>, Rik van Riel <riel@redhat.com>, LKML <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>, Michal Hocko <mhocko@suse.com>
X-Original-Date Wed, 5 Jul 2017 18:56:02 +0200
X-Original-Message-ID <20170705165602.15005-1-mhocko@kernel.org>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1681658

Show key headers only | View raw


From: Michal Hocko <mhocko@suse.com>

"mm: enlarge stack guard gap" has introduced a regression in some rust
and Java environments which are trying to implement their own stack
guard page.  They are punching a new MAP_FIXED mapping inside the
existing stack Vma.

This will confuse expand_{downwards,upwards} into thinking that the stack
expansion would in fact get us too close to an existing non-stack vma
which is a correct behavior wrt. safety. It is a real regression on
the other hand. Let's work around the problem by considering PROT_NONE
mapping as a part of the stack. This is a gros hack but overflowing to
such a mapping would trap anyway an we only can hope that usespace
knows what it is doing and handle it propely.

Fixes: d4d2d35e6ef9 ("mm: larger stack guard gap, between vmas")
Debugged-by: Vlastimil Babka <vbabka@suse.cz>
Cc: stable
Signed-off-by: Michal Hocko <mhocko@suse.com>
---
Hi,
the original thread [1] has grown quite large and also a bit confusing.
At least the rust part should be fixed by this patch. 32b java will
probably need something more on top of this. Btw. JNI environments rely
on MAP_FIXED PROT_NONE as well they were just lucky to not hit the issue
yet I guess.

[1] http://lkml.kernel.org/r/1499126133.2707.20.camel@decadent.org.uk
 mm/mmap.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/mm/mmap.c b/mm/mmap.c
index f60a8bc2869c..2e996cbf4ff3 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2244,7 +2244,8 @@ int expand_upwards(struct vm_area_struct *vma, unsigned long address)
 		gap_addr = TASK_SIZE;
 
 	next = vma->vm_next;
-	if (next && next->vm_start < gap_addr) {
+	if (next && next->vm_start < gap_addr &&
+			(next->vm_flags & (VM_WRITE|VM_READ|VM_EXEC))) {
 		if (!(next->vm_flags & VM_GROWSUP))
 			return -ENOMEM;
 		/* Check that both stack segments have the same anon_vma? */
@@ -2325,7 +2326,8 @@ int expand_downwards(struct vm_area_struct *vma,
 	/* Enforce stack_guard_gap */
 	prev = vma->vm_prev;
 	/* Check that both stack segments have the same anon_vma? */
-	if (prev && !(prev->vm_flags & VM_GROWSDOWN)) {
+	if (prev && !(prev->vm_flags & VM_GROWSDOWN) &&
+			(prev->vm_flags & (VM_WRITE|VM_READ|VM_EXEC))) {
 		if (address - prev->vm_end < stack_guard_gap)
 			return -ENOMEM;
 	}
-- 
2.11.0

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

[PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes in the stack Michal Hocko <mhocko@kernel.org> - 2017-07-05 19:00 +0200
  Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes in  the stack Linus Torvalds <torvalds@linux-foundation.org> - 2017-07-05 19:50 +0200
    Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes  in the stack Michal Hocko <mhocko@kernel.org> - 2017-07-05 20:30 +0200
      Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes in  the stack Linus Torvalds <torvalds@linux-foundation.org> - 2017-07-05 20:40 +0200
        Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes  in the stack Michal Hocko <mhocko@kernel.org> - 2017-07-05 21:00 +0200
          Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes in  the stack Linus Torvalds <torvalds@linux-foundation.org> - 2017-07-05 21:20 +0200
            Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes  in the stack Willy Tarreau <w@1wt.eu> - 2017-07-05 21:20 +0200
          Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes  in the stack Michal Hocko <mhocko@kernel.org> - 2017-07-05 21:20 +0200
      Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes  in the stack Andrew Morton <akpm@linux-foundation.org> - 2017-07-05 23:20 +0200
        Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes in  the stack Linus Torvalds <torvalds@linux-foundation.org> - 2017-07-05 23:50 +0200
        Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes  in the stack Michal Hocko <mhocko@kernel.org> - 2017-07-06 08:50 +0200

csiph-web