FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F5.5.0_cvs 2006-05-23T04:09:12Z 2006-05-23T04:09:12Z cvs2svn cvs2svn@FreeBSD.org 2006-05-23T04:09:12Z urn:sha1:8bf7295cd17b8415c40bde11aa8f5bbbd597e5d6 'RELENG_5_5_0_RELEASE'. This commit was manufactured to restore the state of the 5.5-RELEASE image. 2005-09-28T06:56:14Z Robert Watson rwatson@FreeBSD.org 2005-09-28T06:56:14Z urn:sha1:6bef5a1c4a201f5ace0b2c79ce9bbb80e759db42 Lock the read socket receive buffer when frobbing the sb_state flag on that socket during open, not the write socket receive buffer. Spotted by: ups 2005-09-28T06:48:09Z Robert Watson rwatson@FreeBSD.org 2005-09-28T06:48:09Z urn:sha1:d654d40ebcb19f218a229424b4df88b4d65b53d3 For reasons of consistency (and necessity), assert an exclusive vnode lock on the fifo vnode in fifo_open(): we rely on the vnode lock to serialize access to v_fifoinfo. 2005-09-21T15:35:08Z Robert Watson rwatson@FreeBSD.org 2005-09-21T15:35:08Z urn:sha1:e9ab5752e0d272d845dd0d4582eb2b3b41fe38cc Assert that (vp) is locked in fifo_close(), since we rely on the exclusive vnode lock to synchronize the reference counts on struct fifoinfo. 2005-09-20T13:58:59Z Robert Watson rwatson@FreeBSD.org 2005-09-20T13:58:59Z urn:sha1:f308376070e4d12f30a6b6c3f12fbdbde1706eae The socket pointers in fifoinfo are not permitted to be NULL, so don't check if they are, it just confuses the fifo code more. 2005-09-20T13:33:07Z Robert Watson rwatson@FreeBSD.org 2005-09-20T13:33:07Z urn:sha1:825a392ceeaa5856be806a7151ea67fc31cdf0ad As a result of kqueue locking work, socket buffer locks will always be held when entering a kqueue filter for fifos via a socket buffer event: as such, assert the lock unconditionally rather than acquiring it conditionally. 2005-09-16T09:06:16Z Robert Watson rwatson@FreeBSD.org 2005-09-16T09:06:16Z urn:sha1:8cd3d945535a10a46922a62b6ecc380d472b9321 When a request is made to register a filter on a fifo that doesn't apply to the fifo (i.e., not EVFILT_READ or EVFILT_WRITE), reject it as EINVAL, not by returning 1 (EPERM). 2005-09-16T09:02:25Z Robert Watson rwatson@FreeBSD.org 2005-09-16T09:02:25Z urn:sha1:39d38625d033a1e6b9a62498a63b9a4e7951a485 When a writer opens a fifo, wake up the read socket for read, not the write socket. 2005-09-16T09:01:50Z Robert Watson rwatson@FreeBSD.org 2005-09-16T09:01:50Z urn:sha1:aa67dd1a199fef05dd728c330cea8caa830ad145 Add an assertion that fifo_open() doesn't race against other threads while sleeping to allocate fifo state: due to using the vnode lock to serialize access to a fifo during open, it shouldn't happen (tm). 2005-09-16T09:00:58Z Robert Watson rwatson@FreeBSD.org 2005-09-16T09:00:58Z urn:sha1:9d41d6515c6192b434d2e2233ad2a1b040b648b6 Rather than reaching into the internals of the UNIX domain socket code by calling uipc_connect2() to connect two socket endpoints to create a fifo, call soconnect2().