]> git.proxmox.com Git - mirror_ubuntu-kernels.git/commit
vm: make stack guard page errors return VM_FAULT_SIGSEGV rather than SIGBUS
authorLinus Torvalds <torvalds@linux-foundation.org>
Thu, 29 Jan 2015 19:15:17 +0000 (11:15 -0800)
committerLinus Torvalds <torvalds@linux-foundation.org>
Thu, 29 Jan 2015 19:15:17 +0000 (11:15 -0800)
commit9c145c56d0c8a0b62e48c8d71e055ad0fb2012ba
treeff181616c8f82e8ff3a800bb3cd2a586b8fef4e8
parent33692f27597fcab536d7cbbcc8f52905133e4aa7
vm: make stack guard page errors return VM_FAULT_SIGSEGV rather than SIGBUS

The stack guard page error case has long incorrectly caused a SIGBUS
rather than a SIGSEGV, but nobody actually noticed until commit
fee7e49d4514 ("mm: propagate error from stack expansion even for guard
page") because that error case was never actually triggered in any
normal situations.

Now that we actually report the error, people noticed the wrong signal
that resulted.  So far, only the test suite of libsigsegv seems to have
actually cared, but there are real applications that use libsigsegv, so
let's not wait for any of those to break.

Reported-and-tested-by: Takashi Iwai <tiwai@suse.de>
Tested-by: Jan Engelhardt <jengelh@inai.de>
Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> # "s390 still compiles and boots"
Cc: linux-arch@vger.kernel.org
Cc: stable@vger.kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/memory.c