[PATCH 0/3] properly account for stack randomization and guard gap

From	riel@redhat.com
Newsgroups	linux.kernel
Subject	[PATCH 0/3] properly account for stack randomization and guard gap
Date	2017-06-22 22:10 +0200
Message-ID	<tVgAp-Xd-7@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

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.

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

Thread

[PATCH 0/3] properly account for stack randomization and guard gap riel@redhat.com - 2017-06-22 22:10 +0200
  [PATCH 3/3] powerpc,mmap: properly account for stack randomization in mmap_base riel@redhat.com - 2017-06-22 22:10 +0200
  [PATCH 2/3] arm64/mmap: properly account for stack randomization in mmap_base riel@redhat.com - 2017-06-22 22:10 +0200
  Re: [PATCH 0/3] properly account for stack randomization and guard  gap Ingo Molnar <mingo@kernel.org> - 2017-06-23 10:40 +0200
    Re: [PATCH 0/3] properly account for stack randomization and guard  gap Rik van Riel <riel@redhat.com> - 2017-06-23 17:20 +0200

csiph-web