Re: [RFC][PATCH 1/5] signals: Always place SIGCONT and SIGSTOP on'shared_pending'

From: Matt Fleming
Date: Wed Apr 06 2011 - 09:16:01 EST


On Wed, 6 Apr 2011 14:57:57 +0200
Oleg Nesterov <oleg@xxxxxxxxxx> wrote:

> Argh, sorry, I was not clear.
>
> First of all, only SIGSTOP is never delivered to user-space, other
> sig_kernel_stop() signals can have a handler and in this case, say,
> SIGTTIN doesn't stop but acts like the normal signal. This means you
> can't put it into shared_pending.

Yeah, good point. This patch definitely needs dropping from the series.

> But even SIGSTOP should be routed properly. If the process is ptraced,
> the tracee reports SIGSTOP to the debugger first. This means that
> tkill(SIGSTOP) should be delivered to the right target.

Right, thanks.

--
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/