Don't allow the stack to grow into hugetlb reserved regions
Subsystems (2)
PATCH 1/1 Don't allow the stack to grow into hugetlb reserved regions
When expanding the stack, we don't currently check if the VMA will cross into an area of the address space that is reserved for hugetlb pages. Subsequent faults on the expanded portion of such a VMA will confuse the low-level MMU code, resulting in an OOPS. Check for this.
Signed-off-by Adam Litke <[email protected]>
---
mm/mmap.c | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-)
mm/mmap.c +7 -0
@@ -1477,6 +1477,7 @@ static int acct_stack_growth(struct vm_area_struct * vma, unsigned long size, un {struct mm_struct *mm = vma->vm_mm;struct rlimit *rlim = current->signal->rlim; +unsigned long new_start;/* address space limit tests */ if (!may_expand_vm (mm, grow))
@@ -1496,6 +1497,12 @@ static int acct_stack_growth(struct vm_area_struct * vma, unsigned long size, unreturn -ENOMEM ; } +/* Check to make the stack will not grow into a hugetlb-only region. */ + new_start = (vma->vm_flags &VM_GROWSUP ) ? vma->vm_start : + vma->vm_end - size; +if (is_hugepage_only_range (vma->vm_mm, new_start, size)) +return -EFAULT ; +/* * Overcommit.. This must be the final test, as it will * update security statistics.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>