diff options
| author | Hugh Dickins <hugh@veritas.com> | 2009-04-16 21:58:12 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-04-16 14:41:25 -0700 |
| commit | 05fa199d45c54a9bda7aa3ae6537253d6f097aa9 (patch) | |
| tree | cfdcdd04bfcef7d0dcb47fad93ba8fa676349dd3 /mm/mmap.c | |
| parent | 05f54c13cd0c33694eec39a265475c5d6cf223cf (diff) | |
| download | kernel_samsung_smdk4412-05fa199d45c54a9bda7aa3ae6537253d6f097aa9.tar.gz kernel_samsung_smdk4412-05fa199d45c54a9bda7aa3ae6537253d6f097aa9.tar.bz2 kernel_samsung_smdk4412-05fa199d45c54a9bda7aa3ae6537253d6f097aa9.zip | |
mm: pass correct mm when growing stack
Tetsuo Handa reports seeing the WARN_ON(current->mm == NULL) in
security_vm_enough_memory(), when do_execve() is touching the
target mm's stack, to set up its args and environment.
Yes, a UMH_NO_WAIT or UMH_WAIT_PROC call_usermodehelper() spawns
an mm-less kernel thread to do the exec. And in any case, that
vm_enough_memory check when growing stack ought to be done on the
target mm, not on the execer's mm (though apart from the warning,
it only makes a slight tweak to OVERCOMMIT_NEVER behaviour).
Reported-by: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Signed-off-by: Hugh Dickins <hugh@veritas.com>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/mmap.c')
| -rw-r--r-- | mm/mmap.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mm/mmap.c b/mm/mmap.c index 4a3841186c1..3303d1ba8e8 100644 --- a/mm/mmap.c +++ b/mm/mmap.c @@ -1575,7 +1575,7 @@ static int acct_stack_growth(struct vm_area_struct *vma, unsigned long size, uns * Overcommit.. This must be the final test, as it will * update security statistics. */ - if (security_vm_enough_memory(grow)) + if (security_vm_enough_memory_mm(mm, grow)) return -ENOMEM; /* Ok, everything looks good - let it rip */ |