Commit 00a905e6 authored by Jeff Dike's avatar Jeff Dike Committed by Linus Torvalds
Browse files

uml: don't kill pid 0

A bit of defensive programming - during development, it ocassionally
happens that a call to init_new_context is missed, resulting in
context holding a host pid of zero.  When that address space is torn
down, destroy_context does a kill(0), which instantly kills the whole
UML without any errors whatsoever.

This patch add a check for pids less than 2, to also catch 1 and
negative pids.
Signed-off-by: default avatarJeff Dike <>
Signed-off-by: default avatarAndrew Morton <>
Signed-off-by: default avatarLinus Torvalds <>
parent 1aa351a3
......@@ -164,8 +164,20 @@ void destroy_context(struct mm_struct *mm)
if (proc_mm)
else {
* If init_new_context wasn't called, this will be
* zero, resulting in a kill(0), which will result in the
* whole UML suddenly dying. Also, cover negative and
* 1 cases, since they shouldn't happen either.
if (mmu-> < 2) {
printk(KERN_ERR "corrupt mm_context - pid = %d\n",
os_kill_ptraced_process(mmu->, 1);
if (skas_needs_stub)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment