aboutsummaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorwill schmidt <will_schmidt@vnet.ibm.com>2007-06-12 11:19:01 -0400
committerPaul Mackerras <paulus@samba.org>2007-06-14 08:29:59 -0400
commiteffe24bdd41ef790b30c9ac02ede3703937c6ba0 (patch)
tree558fde1f554a95893176f3243df34629dd4b86a7 /arch
parentd8c391a5593aca5bea002bcaaec16c7bbd6ec853 (diff)
[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')
-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 bfe901353142..fd176840a595 100644
--- a/arch/powerpc/mm/fault.c
+++ b/arch/powerpc/mm/fault.c
@@ -381,7 +381,7 @@ out_of_memory:
381 } 381 }
382 printk("VM: killing process %s\n", current->comm); 382 printk("VM: killing process %s\n", current->comm);
383 if (user_mode(regs)) 383 if (user_mode(regs))
384 do_exit(SIGKILL); 384 do_group_exit(SIGKILL);
385 return SIGKILL; 385 return SIGKILL;
386 386
387do_sigbus: 387do_sigbus: