Ed Schouten c0086bf202 Serialize write() calls on TTYs. ... Just like the old TTY layer, the current MPSAFE TTY layer does not make any attempt to serialize calls of write(). Data is copied into the kernel in 256 (TTY_STACKBUF) byte chunks. If a write() call occurs at the same time, the data may interleave. This is especially likely when the TTY starts blocking, because the output queue reaches the high watermark. I've implemented this by adding a new flag, TTY_BUSY_OUT, which is used to mark a TTY as having a thread stuck in write(). Because I don't want non-blocking processes to be possibly blocked by a sleeping thread, I'm still allowing it to bypass the protection. According to this message, the Linux kernel returns EAGAIN in such cases, but I think that's a little too restrictive: http://kerneltrap.org/index.php?q=mailarchive/linux-kernel/2007/5/2/85418/thread PR: kern/118287		2009-02-11 16:28:49 +00:00
..
Makefile
pstat.8	Serialize write() calls on TTYs.	2009-02-11 16:28:49 +00:00
pstat.c	Serialize write() calls on TTYs.	2009-02-11 16:28:49 +00:00