Richard Weinberger 91d44ff860 um: Cleanup SIGTERM handling ... Richard reported that some UML processes survive if the UML main process receives a SIGTERM. This issue was caused by a wrongly placed signal(SIGTERM, SIG_DFL) in init_new_thread_signals(). It disabled the UML exit handler accidently for some processes. The correct solution is to disable the fatal handler for all UML helper threads/processes. Such that last_ditch_exit() does not get called multiple times and all processes can exit due to SIGTERM. Reported-and-tested-by: Richard W.M. Jones <rjones@redhat.com> Signed-off-by: Richard Weinberger <richard@nod.at>		2013-09-07 10:56:58 +02:00
..
skas
aio.h
arch.h
as-layout.h
common-offsets.h	nohz: Rename CONFIG_NO_HZ to CONFIG_NO_HZ_COMMON	2013-04-03 13:56:03 +02:00
elf_user.h
frame_kern.h	um: siginfo cleanup	2013-07-19 11:31:36 +02:00
init.h
irq_kern.h
irq_user.h
kern_util.h
kern.h
longjmp.h
mem_user.h
mem.h
net_kern.h
net_user.h
os.h	um: Cleanup SIGTERM handling	2013-09-07 10:56:58 +02:00
ptrace_user.h
registers.h
sigio.h
skas_ptrace.h
um_malloc.h
user.h