ce10f4da5b
neither it does send any SIGIO for pipes. If async I/O was requested, we keep the SS_ASYNC in struct socket flag set, but we clear SB_ASYNC flags on the sending buffer (for socket), and on the sending and the receiving buffer (for pipes). Because we do not alter to SS_ASYNC in struct socket, the Linux process keeps a consistent view of async I/O status if it attemps to read the async flag (SS_ASYNC) This async I/O problem does matters, since some Linux a programs such as the JDK request async I/O on pipes, but they fail if they happen to get a SIGIO to the write end of the pipe. |
||
---|---|---|
bin | ||
crypto | ||
dist | ||
distrib | ||
etc | ||
games | ||
gnu | ||
include | ||
lib | ||
libexec | ||
regress | ||
sbin | ||
share | ||
sys | ||
usr.bin | ||
usr.sbin | ||
Makefile | ||
Makefile.inc | ||
UPDATING |