Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753932AbdFVUBW (ORCPT ); Thu, 22 Jun 2017 16:01:22 -0400 Received: from shelob.surriel.com ([96.67.55.147]:50024 "EHLO shelob.surriel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753794AbdFVUAt (ORCPT ); Thu, 22 Jun 2017 16:00:49 -0400 From: riel@redhat.com To: linux-kernel@vger.kernel.org Cc: akpm@linux-foundation.org, mingo@kernel.org, will.deacon@arm.com, danielmicay@gmail.com, benh@kernel.crashing.org, hughd@google.com Subject: [PATCH 0/3] properly account for stack randomization and guard gap Date: Thu, 22 Jun 2017 16:00:30 -0400 Message-Id: <20170622200033.25714-1-riel@redhat.com> X-Mailer: git-send-email 2.9.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 483 Lines: 11 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.