On 05/30, Thomas Gleixner wrote:
>
> So I found at least some explanation by studying the spec some more.
>
> There are two variants of ignored signals:
>
> 1) handler is SIG_IGN
>
> 2) handler is SIG_DFL and default action is 'ignore'
Yes, and note that sys_rt_sigaction() discard the pending signal in both cases.
So even with this change the logic won't look 100% consistent.
I can't comment, I never tried to understand the rationality behind the current
behaviour. But at least the sending path should never drop a blocked SIG_DFL
signal, there is no other way to ensure you won't miss a signal during exec.
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -70,6 +70,13 @@ static int sig_handler_ignored(void __us
> (handler == SIG_DFL && sig_kernel_ignore(sig));
> }
>
> +static int sig_handler_is_sigign(struct task_struct *t, int sig)
> +{
> + void __user *handler = sig_handler(t, sig);
> +
> + return handler == SIG_IGN;
> +}
> +
> static int sig_task_ignored(struct task_struct *t, int sig, bool force)
> {
> void __user *handler;
> @@ -91,7 +98,7 @@ static int sig_ignored(struct task_struc
> * unblocked.
> */
> if (sigismember(&t->blocked, sig) || sigismember(&t->real_blocked, sig))
> - return 0;
> + return sig_handler_is_sigign(t, sig);
we can probably make a simpler change, but this doesn't matter.
Obviously this is a user-visible change and it can break something. Say, an
application does sigwaitinfo(SIGCHLD) and SIGCHLD is ignored (SIG_IGN), this
will no longer work.
I won't argue, but perhaps it is too late change this historical behaviour.
Although perhaps we can cleanup do_sigtimedwait() for the start. ->real_blocked
doesn't look nice. I think we can replace it with task->sigwait_mask and then
change sig_handler() to do
sigismember(sigwait_mask, sig) ? SIG_ERR :
t->sighand->action[sig - 1].sa.sa_handler;
this needs other changes, say, sig_fatal() will need to use sig_handler() too.
Then it would be more safe to drop the SIG_IGN signals unconditionally.
Oleg.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
