properly account for stack randomization and guard gap
Status from this message: [merged] powerpcmmap-properly-account-for-stack-randomization-in-mmap_base.patch removed from -mm tree
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 All 3 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | x86/mmap: properly account for stack randomization in mmap_basearch/ | +6 | 0 replies | Applied |
| 2/3 | arm64/mmap: properly account for stack randomization in mmap_basearch/ | +6 | 0 replies | Applied |
| 3/3 | powerpc,mmap: properly account for stack randomization in mmap_basearch/ | +19 | 0 replies | Applied |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Ingo Molnar |
|---|---|
| Series | A-b |
| 1/3 | |
| 2/3 | |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] properly account for stack randomization and guard gap
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.