lkml.org 
[lkml]   [2006]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: synchronous signal in the blocked signal context


On Mon, 31 Jul 2006, Siddha, Suresh B wrote:
>
> This patch (b0423a0d9cc836b2c3d796623cd19236bfedfe63)
>
> [PATCH] Remove duplicate code in signal.c
>
> reverts a patch introduced by Linus long time back.

Good catch.

> Was this intentional?
>
> With the current mainline code, SIGSEGV inside a SIGSEGV handler will endup
> in linux handling endless recursive faults.
>
> Just wondering if this has been discussed before and is intentional.

It certainly wasn't discussed, and I don't think it was intentional. We
should _not_ just unblock a blocked signal. We should kill the process,
because sending the signal is actually very very wrong.

Paul? Should I just revert, or did you have some deeper reason for it?

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-11-18 23:46    [W:0.045 / U:0.336 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site