summaryrefslogtreecommitdiffstats
path: root/arch/powerpc/mm/fault.c
diff options
context:
space:
mode:
authorwill schmidt <will_schmidt@vnet.ibm.com>2007-06-13 01:19:01 +1000
committerPaul Mackerras <paulus@samba.org>2007-06-14 22:29:59 +1000
commiteffe24bdd41ef790b30c9ac02ede3703937c6ba0 (patch)
tree558fde1f554a95893176f3243df34629dd4b86a7 /arch/powerpc/mm/fault.c
parentd8c391a5593aca5bea002bcaaec16c7bbd6ec853 (diff)
downloadop-kernel-dev-effe24bdd41ef790b30c9ac02ede3703937c6ba0.zip
op-kernel-dev-effe24bdd41ef790b30c9ac02ede3703937c6ba0.tar.gz
[POWERPC] During VM oom condition, kill all threads in process group
We have had complaints where a threaded application is left in a bad state after one of it's threads is killed when we hit a VM: out_of_memory condition. Killing just one of the process threads can leave the application in a bad state, whereas killing the entire process group would allow for the application to restart, or be otherwise handled, and makes it very obvious that something has gone wrong. This change allows the entire process group to be taken down, rather than just the one thread. lightly tested on powerpc Signed-off-by: Will <will_schmidt@vnet.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'arch/powerpc/mm/fault.c')
-rw-r--r--arch/powerpc/mm/fault.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/powerpc/mm/fault.c b/arch/powerpc/mm/fault.c
index bfe9013..fd17684 100644
--- a/arch/powerpc/mm/fault.c
+++ b/arch/powerpc/mm/fault.c
@@ -381,7 +381,7 @@ out_of_memory:
}
printk("VM: killing process %s\n", current->comm);
if (user_mode(regs))
- do_exit(SIGKILL);
+ do_group_exit(SIGKILL);
return SIGKILL;
do_sigbus:
OpenPOWER on IntegriCloud