Re: SIGCONT misbehaviour in Linux

Andi Kleen (ak@muc.de)
10 Dec 1999 05:05:26 +0100

paire@ri.silicomp.fr (Eric Paire) writes:
>
> The behaviour of the Linux kernel for that is that it always returns
> EINTR when a blocking system call has been interrupted by a signal,
> whether there was a signal handler attached *OR NOT*. THIS IS THE
> REASON WHY I STATED THAT LINUX IS NOT POSIX-COMPLIANT ON THIS SPECIAL
> SIGNAL MANAGEMENT.

send_sig_info has this code

/* Optimize away the signal, if it's a signal that can be
handled immediately (ie non-blocked and untraced) and
that is ignored (either explicitly or by default). */

if (ignored_signal(sig, t))
goto out;

So when the signal is blocked it should never even reach the process.

-Andi

-- 
This is like TV. I don't like TV.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/