original_kernel/arch/x86_64/ia32
Roland McGrath 0928d6ef7f [PATCH] x86_64: never block forced SIGSEGV
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>
2005-06-23 09:45:13 -07:00
..
Makefile
fpu32.c
ia32_aout.c [PATCH] Avoiding mmap fragmentation 2005-06-21 18:46:16 -07:00
ia32_binfmt.c [PATCH] x86_64: TASK_SIZE fixes for compatibility mode processes 2005-06-21 18:46:12 -07:00
ia32_ioctl.c
ia32_signal.c [PATCH] x86_64: never block forced SIGSEGV 2005-06-23 09:45:13 -07:00
ia32entry.S
ipc32.c
ptrace32.c
sys_ia32.c
syscall32.c [PATCH] x86_64: Use a VMA for the 32bit vsyscall 2005-04-16 15:24:55 -07:00
tls32.c
vsyscall-sigreturn.S
vsyscall-syscall.S
vsyscall-sysenter.S
vsyscall.lds [PATCH] x86_64: fix PT_NOTE addition to IA32 vDSO 2005-04-28 22:47:29 -07:00