Re: [PATCH 4/4] signalfd: make it group-wide, fix posix-timers scheduling

2007-08-14 Thread Oleg Nesterov
On 08/13, Oleg Nesterov wrote: > > Sorry, the patch is not complete. I forgot about signalfd_poll() and somehow I > forgot to actually tweak de_thread(). I'll send a new one tomorrow. > > Something should be done for 2.6.23, imho. Slightly tested. This all needs furher cleanups (for example,

Re: [PATCH 4/4] signalfd: make it group-wide, fix posix-timers scheduling

2007-08-14 Thread Oleg Nesterov
On 08/13, Oleg Nesterov wrote: Sorry, the patch is not complete. I forgot about signalfd_poll() and somehow I forgot to actually tweak de_thread(). I'll send a new one tomorrow. Something should be done for 2.6.23, imho. Slightly tested. This all needs furher cleanups (for example,

Re: [PATCH 4/4] signalfd: make it group-wide, fix posix-timers scheduling

2007-08-13 Thread Oleg Nesterov
On 08/12, Oleg Nesterov wrote: > > Untested, user visible change. > > With this patch any thread can dequeue its own private signals via signalfd, > even if it was created by another sub-thread. > > To do so, we pass "current" to dequeue_signal() if the caller is from the same > thread group.

Re: [PATCH 4/4] signalfd: make it group-wide, fix posix-timers scheduling

2007-08-13 Thread Oleg Nesterov
On 08/12, Oleg Nesterov wrote: Untested, user visible change. With this patch any thread can dequeue its own private signals via signalfd, even if it was created by another sub-thread. To do so, we pass current to dequeue_signal() if the caller is from the same thread group. This also