Re: [PATCH] signal: protect SIGNAL_UNKILLABLE from unintentional clearing.
From: Oleg Nesterov
Date: Thu Nov 17 2016 - 14:04:26 EST
On 11/16, Jamie Iles wrote:
> This can result in init becoming stoppable/killable after tracing. For
> example, running:
> while true; do kill -STOP 1; done &
> strace -p 1
> and then stopping strace and the kill loop will result in init being
> left in state TASK_STOPPED. Sending SIGCONT to init will resume it, but
> init will now respond to future SIGSTOP signals rather than ignoring
Yes, and a lot more... I forgot about these problems again.
Jamie, sorry for delay, I'll try to read the patch and reply tomorrow.