Re: Fix signalfd interaction with thread-private signals

[Linus Torvalds]

On Thu, 21 Jun 2007, Oleg Nesterov wrote:
> 
> Yes, force_sig() unblocks and un-ignores the signal. However, unlike group-wide
> signals, thread-specific signals do not convert themselves to SIGKILL on delivery.
> The target thread should dequeue SIGSEGV and then it calls do_group_exit().

No it couldn't.

Why? Because the target thread is the one that *caused* the SIGSEGV in the 
first place. It's not going to dequeue *anything*. It's either going to 
take the SIGSEGV, or it's going to get another SIGSEGV and now it's no 
longer masked/handled and it's going to die.

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