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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Fix signalfd interaction with thread-private signals
- From: Oleg Nesterov <[email protected]>
- Re: Fix signalfd interaction with thread-private signals
- References:
- Re: And now for something _totally_ different: Linux v2.6.22-rc5
- From: Nicholas Miell <[email protected]>
- Re: And now for something _totally_ different: Linux v2.6.22-rc5
- From: Davide Libenzi <[email protected]>
- Re: And now for something _totally_ different: Linux v2.6.22-rc5
- From: Benjamin Herrenschmidt <[email protected]>
- Re: And now for something _totally_ different: Linux v2.6.22-rc5
- From: Linus Torvalds <[email protected]>
- Re: Fix signalfd interaction with thread-private signals
- From: Oleg Nesterov <[email protected]>
- Re: Fix signalfd interaction with thread-private signals
- From: Benjamin Herrenschmidt <[email protected]>
- Re: Fix signalfd interaction with thread-private signals
- From: Oleg Nesterov <[email protected]>
- Re: Fix signalfd interaction with thread-private signals
- From: Benjamin Herrenschmidt <[email protected]>
- Re: Fix signalfd interaction with thread-private signals
- From: Oleg Nesterov <[email protected]>
- Re: Fix signalfd interaction with thread-private signals
- From: Linus Torvalds <[email protected]>
- Re: Fix signalfd interaction with thread-private signals
- From: Oleg Nesterov <[email protected]>
- Re: And now for something _totally_ different: Linux v2.6.22-rc5
- Prev by Date: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?
- Next by Date: Re: [PATCH 19/19] ide: use PIO/MMIO operations directly where possible
- Previous by thread: Re: Fix signalfd interaction with thread-private signals
- Next by thread: Re: Fix signalfd interaction with thread-private signals
- Index(es):
 |