Messages in this thread | | | Date | Wed, 20 Jun 2007 10:38:04 -0700 (PDT) | From | Linus Torvalds <> | Subject | Re: Fix signalfd interaction with thread-private signals |
| |
On Wed, 20 Jun 2007, Oleg Nesterov wrote: > > Also, suppose that some thread does > > for (;;) > signal(SIGSEGV, SIG_IGN); > > Now we have the same situation. do_sigaction() can steal SIGSEGV from > another thread.
Actually, that shouldn't be possible.
See "force_sig_info()". It does not allow blocking or ignoring forced signals. We will reset such a signal handler to SIG_DFL, and unlock it.
So if you get a SIGSEGV while SIGSEGV's are blocked or ignored, the kernel *will* kill you. No questions asked.
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/
| |