Messages in this thread | | | Date | Tue, 19 Jun 2007 18:06:46 +0400 | From | Oleg Nesterov <> | Subject | Re: Fix signalfd interaction with thread-private signals |
| |
On 06/19, Benjamin Herrenschmidt wrote: > > On Tue, 2007-06-19 at 13:14 +0400, Oleg Nesterov wrote: > > > The commited "Fix signalfd interaction with thread-private signals" > > (commit caec4e8dc85e0644ec24aeb36285e1ba02da58cc) doesn't implement > > this. > > Indeed, if you want what Davide described, you need to also change > signalfd side. The patch I did merely prevents another thread from > dequeuing somebody else private signals.
Yes I see, but why do we need this change? Yes, we can dequeue SIGSEGV from another thread. Just don't do it if you have a handler for SIGSEGV?
Oleg.
- 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/
| |