Re: [PATCH net-next v2 2/6] net: Introduce read_sock_rectype proto_ops for control record delivery
Jakub Kicinski <[email protected]> Thu, 30 Jul 2026 16:34:57 -0700
| Newsgroups | dev.linux.lists.kernel-tls-handshake,org.kernel.vger.linux-kselftest,org.kernel.vger.linux-nfs,org.kernel.vger.netdev |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 31 Jul 2026 01:09:33 +0200 Sabrina Dubroca wrote: > To avoid that, you'd have to run recvmsg-nocmsg/read_sock to get all > the DATA out, then once you know the next chunk of payload is a > control record (and hopefully nothing else is reading from your > socket), one recvmsg+cmsg into a separate buffer. I guess the difference in perspective stems from a fact that I'd look at a socket as a stream one reads and dispatches work based on the input. Not an abstraction layer that by itself dispatches different handlers for different message types.