summaryrefslogtreecommitdiff
path: root/lib/is_single_threaded.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2015-01-11 22:33:57 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2015-01-11 22:33:57 +0300
commit690eac53daff34169a4d74fc7bfbd388c4896abb (patch)
tree72d9df754ed4291de6287c30502dd66a04aa6845 /lib/is_single_threaded.c
parent4850d37d3a7c049f7dc3eb09d7ae4e5553ac521b (diff)
downloadlinux-690eac53daff34169a4d74fc7bfbd388c4896abb.tar.xz
mm: Don't count the stack guard page towards RLIMIT_STACK
Commit fee7e49d4514 ("mm: propagate error from stack expansion even for guard page") made sure that we return the error properly for stack growth conditions. It also theorized that counting the guard page towards the stack limit might break something, but also said "Let's see if anybody notices". Somebody did notice. Apparently android-x86 sets the stack limit very close to the limit indeed, and including the guard page in the rlimit check causes the android 'zygote' process problems. So this adds the (fairly trivial) code to make the stack rlimit check be against the actual real stack size, rather than the size of the vma that includes the guard page. Reported-and-tested-by: Chih-Wei Huang <cwhuang@android-x86.org> Cc: Jay Foad <jay.foad@gmail.com> Cc: stable@kernel.org # to match back-porting of fee7e49d4514 Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/is_single_threaded.c')
0 files changed, 0 insertions, 0 deletions