narayan@tandem.UUCP (Narayan Mohanram) (04/09/88)
In tcpinput, I noticed that there was support for SO_OOBINLINE. But it has not been carried through to tcp_usrreq (). The case PRU_RCVOOB, needs to create mbufs, and chain them on to the original mbuf chain (m_copy) up to so_oobmark. This will cause soreceive to do the right thing when it is doing an soreceive MSG_OOB. This fix does not seem to exist even in the new 4.3 updates recently posted THE SUPREME DALEK from SCAROS
karels@OKEEFFE.BERKELEY.EDU (Mike Karels) (04/11/88)
You're wrong. The case PRU_RCVOOB no longer has anything to do with out-of-band data if SO_OOBINLINE is set. As out-of-band data is never removed from incoming packets, it is not stored in the protocol and is not retrieved from there. Calling recv with MSG_OOB with the SO_OOBINLINE option set is wrong. Mike
jcw@wdl1.UUCP (John C Williams) (04/13/88)
Mike Karels, Adding a response unrelated to your response to someone else's article, with the net listening in, I believe qualifies as indirect communication --assuming this note comes to your attention. I can ping your hosts to death, but my mail comes bouncing back. (This ought to be a song!) Question (of possible interest to others): When is the book on UNIX BSD 4.3 Internals coming out? Title, publisher, etc.? Regards (and thanks for the net's indulgence), John jcw@ford-wdl1.arpa