From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754203AbdFWIf2 (ORCPT ); Fri, 23 Jun 2017 04:35:28 -0400 Received: from mail-wr0-f196.google.com ([209.85.128.196]:33864 "EHLO mail-wr0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751231AbdFWIfZ (ORCPT ); Fri, 23 Jun 2017 04:35:25 -0400 Date: Fri, 23 Jun 2017 10:35:21 +0200 From: Ingo Molnar To: riel@redhat.com Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, will.deacon@arm.com, danielmicay@gmail.com, benh@kernel.crashing.org, hughd@google.com, Linus Torvalds , Michal Hocko , Dave Jones , Oleg Nesterov Subject: Re: [PATCH 0/3] properly account for stack randomization and guard gap Message-ID: <20170623083521.f62me7efrm4ygawq@gmail.com> References: <20170622200033.25714-1-riel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170622200033.25714-1-riel@redhat.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * riel@redhat.com wrote: > When RLIMIT_STACK is larger than the minimum gap enforced by > mmap_base(), it is possible for the kernel to place the mmap > area where the stack wants to grow, resulting in the stack > not being able to use the space that should have been allocated > to it through RLIMIT_STACK. > > This series ensures that x86, ARM64, and PPC have at least > RLIMIT_STACK + stack randomization + the stack guard gap > space available for the stack. > > s390 seems to be ok. I have not checked other architectures. x86 patch LGTM: Acked-by: Ingo Molnar ... but I suspect this wants to go via -mm or Linus directly? Thanks, Ingo