RE: Who changed /proc// in 2.6.0-test5-bk9? (SIGPIPE?)

Linus Torvalds
2003-10-08T02:58:21Z

On Tue, 7 Oct 2003, Robert White wrote:
>
> If all the CLONE_THREAD members of a process (automatically) have the same
> signal handling code/context but not the same list of file descriptors, what
> happens when a file descriptor posts SIGPIPE or SIGIO (etc.) to a process?

You have to explicitly _ask_ for SIGIO. If you do so, and you don't share
file descriptors, that's _your_ problem.

But it does indeed have perfectly valid semantics - the signal may well
just wake up a thread: and in fact, as most IO is illegal in signal
handler context anyway, it usually has to.

Clearly, if you have per-thread file descriptors, you have to keep track
of which thread is doing what.

Linus