aboutsummaryrefslogtreecommitdiffstats
path: root/include/asm-i386/mach-es7000
diff options
context:
space:
mode:
authorRoland McGrath <roland@redhat.com>2005-06-23 03:08:21 -0400
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-06-23 12:45:09 -0400
commit7c1def1652c6c1a95eafca2991baace34afaed0f (patch)
tree0175c6babb39233a5cbbdf3c8ca9027180f580ed /include/asm-i386/mach-es7000
parent1946089a109251655c5438d92c539bd2930e71ea (diff)
[PATCH] i386: never block forced SIGSEGV
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> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include/asm-i386/mach-es7000')
0 files changed, 0 insertions, 0 deletions