include/uapi/linux/vm_sockets.h

File Facts

System

Linux kernel

Corpus path

include/uapi/linux/vm_sockets.h

Extension

.h

Size

7501 bytes

Lines

216

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• sys/socket.h
• linux/socket.h
• linux/types.h

Detected Declarations

• struct sockaddr_vm

Annotated Snippet

struct sockaddr_vm {
	__kernel_sa_family_t svm_family;
	unsigned short svm_reserved1;
	unsigned int svm_port;
	unsigned int svm_cid;
	__u8 svm_flags;
	unsigned char svm_zero[sizeof(struct sockaddr) -
			       sizeof(sa_family_t) -
			       sizeof(unsigned short) -
			       sizeof(unsigned int) -
			       sizeof(unsigned int) -
			       sizeof(__u8)];
};

#define IOCTL_VM_SOCKETS_GET_LOCAL_CID		_IO(7, 0xb9)

/* MSG_ZEROCOPY notifications are encoded in the standard error format,
 * sock_extended_err. See Documentation/networking/msg_zerocopy.rst in
 * kernel source tree for more details.
 */

/* 'cmsg_level' field value of 'struct cmsghdr' for notification parsing
 * when MSG_ZEROCOPY flag is used on transmissions.
 */

#define SOL_VSOCK	287

/* 'cmsg_type' field value of 'struct cmsghdr' for notification parsing
 * when MSG_ZEROCOPY flag is used on transmissions.
 */

#define VSOCK_RECVERR	1

#endif /* _UAPI_VM_SOCKETS_H */

Annotation

• Immediate include surface: `sys/socket.h`, `linux/socket.h`, `linux/types.h`.
• Detected declarations: `struct sockaddr_vm`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.