ps (for example,
__exit_signal()->signalfd_detach_locked() is not needed unless we are
group_leader), but this code be done later.
[PATCH 4/4] signalfd: make it group-wide, fix posix-timers scheduling
With this patch any thread can dequeue its own private signals via signalfd,
even if it was crea
,
__exit_signal()-signalfd_detach_locked() is not needed unless we are
group_leader), but this code be done later.
[PATCH 4/4] signalfd: make it group-wide, fix posix-timers scheduling
With this patch any thread can dequeue its own private signals via signalfd,
even if it was created by another sub-thread
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.
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
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 fixes the scheduling of posix timers
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 fixes the scheduling of posix timers
6 matches
Mail list logo
