Messages in this thread | | | Date | Sun, 29 Sep 2002 03:47:37 -0700 | From | Roland McGrath <> | Subject | Re: 2.5.39: Signal delivery to thread groups: Bug or feature |
| |
> we still have one more problem left in the signal handling area: atomicity > of signal delivery. Eg. right now it's possible to have a signal 'in > flight' for one specific thread, which manages to block it before handling > the signal. What should the behavior be in that case? Does POSIX say > anything about this?
Assuming you are talking about a process-global signal (not pthread_kill), then POSIX does not permit this race condition. If there is any thread that can take the signal (i.e. not blocking it, or is sigwait'ing for it), then one such thread must take the signal. The selection of the thread and it beginning its action (i.e. choosing a signal handler, and saving the signal mask the signal handler will restore on its return; or process death) must be atomic with respect to that thread blocking the signal.
- 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/
| |