mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-18 10:13:57 +08:00
0928d6ef7f
This is the x86_64 version of the signal fix I just posted for i386. This problem was first noticed on PPC and has already been fixed there. But the exact same issue applies to other platforms in the same way. The signal blocking for sa_mask and the handled signal takes place after the handler setup. When the stack is bogus, the handler setup forces a SIGSEGV. But then this will be blocked, and returning to user mode will fault again and iterate. This patch fixes the problem by checking whether signal handler setup failed, and not doing the signal-blocking if so. This copies what was done in the ppc code. I think all architectures' signal handler setup code follows this pattern and needs the change. Signed-off-by: Roland McGrath <roland@redhat.com> Cc: Andi Kleen <ak@suse.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org> |
||
|---|---|---|
| .. | ||
| fpu32.c | ||
| ia32_aout.c | ||
| ia32_binfmt.c | ||
| ia32_ioctl.c | ||
| ia32_signal.c | ||
| ia32entry.S | ||
| ipc32.c | ||
| Makefile | ||
| ptrace32.c | ||
| sys_ia32.c | ||
| syscall32.c | ||
| tls32.c | ||
| vsyscall-sigreturn.S | ||
| vsyscall-syscall.S | ||
| vsyscall-sysenter.S | ||
| vsyscall.lds | ||