From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f72.google.com (mail-wm0-f72.google.com [74.125.82.72]) by kanga.kvack.org (Postfix) with ESMTP id 67888680FBC for ; Wed, 5 Jul 2017 14:28:55 -0400 (EDT) Received: by mail-wm0-f72.google.com with SMTP id b189so30493717wmb.12 for ; Wed, 05 Jul 2017 11:28:55 -0700 (PDT) Received: from mx1.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id j83si17164216wma.149.2017.07.05.11.28.53 for (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 05 Jul 2017 11:28:53 -0700 (PDT) Date: Wed, 5 Jul 2017 20:28:49 +0200 From: Michal Hocko Subject: Re: [PATCH] mm: mm, mmap: do not blow on PROT_NONE MAP_FIXED holes in the stack Message-ID: <20170705182849.GA18027@dhcp22.suse.cz> References: <20170705165602.15005-1-mhocko@kernel.org> 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: Linus Torvalds Cc: Andrew Morton , Vlastimil Babka , Ben Hutchings , Willy Tarreau , Oleg Nesterov , Rik van Riel , LKML , linux-mm On Wed 05-07-17 10:43:27, Linus Torvalds wrote: > On Wed, Jul 5, 2017 at 9:56 AM, Michal Hocko wrote: > > > > "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. > > Hmm. What version is this patch against? It doesn't seem to match my 4.12 tree. Dohh, that was on mmotm which has a clean up by Oleg which reorganizes the code a bit. This is on top of the current master ---