4b84c69b5f
Have most signals go through an arch-provided handler which recovers the sigcontext and then calls a generic handler. This replaces the ARCH_GET_SIGCONTEXT macro, which was somewhat fragile. On x86_64, recovering %rdx (which holds the sigcontext pointer) must be the first thing that happens. sig_handler duly invokes that first, but there is no guarantee that I can see that instructions won't be reordered such that %rdx is used before that. Having the arch provide the handler seems much more robust. Some signals in some parts of UML require their own handlers - these places don't call set_handler any more. They call sigaction or signal themselves. Signed-off-by: Jeff Dike <jdike@addtoit.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org> |
||
|---|---|---|
| .. | ||
| archsetjmp.h | ||
| checksum.h | ||
| faultinfo.h | ||
| kernel-offsets.h | ||
| ptrace_user.h | ||
| ptrace.h | ||
| sc.h | ||
| sigcontext.h | ||
| skas_ptrace.h | ||
| stub.h | ||
| syscalls.h | ||
| thread.h | ||
| tls.h | ||