On Sun, 17 Jun 2007, Nicholas Miell wrote: > On Sun, 2007-06-17 at 10:01 -0700, Davide Libenzi wrote: > > On Sun, 17 Jun 2007, Nicholas Miell wrote: > > > > > On Sat, 2007-06-16 at 20:33 -0700, Linus Torvalds wrote: > > > > In a stunning turn of events, I've actually been able to make another > > > > -rc > > > > release despite all the discussion (*cough*flaming*cough*) about other > > > > issues, and we now have a brand-spanking-new Linux 2.6.22-rc5 release > > > > out there! > > > > > > > > > > signalfd still has the broken behavior w.r.t. signal delivery to > > > threads. > > > > > > Is this going to get fixed before 2.6.22 proper is released, or should > > > it just be disabled entirely so no userspace apps grow to depend on > > > current wrong behavior? > > > > At the moment, with Ben's patch applied, signalfd can see all group-sent > > signals, and locally-directed thread signals. > > But there's still no way for multiple threads to read from a single > signalfd and get their own thread-specific signals in addition to > process-wide signals, right? I think this was agreed to be the least > surprising behavior.
Multiple threads can wait on the signalfd. Each one will dequeue either its own private signals (tsk->pending) or the process shared ones (tsk->signal->shared_pending). This will be the behaviour once Ben's patch is applied. - Davide - 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/
