net/vmw_vsock/diag.c
Source file repositories/reference/linux-study-clean/net/vmw_vsock/diag.c
File Facts
- System
- Linux kernel
- Corpus path
net/vmw_vsock/diag.c- Extension
.c- Size
- 4175 bytes
- Lines
- 181
- Domain
- Networking Core
- Bucket
- Sockets, Protocols, Packet Path, And Network Policy
- Inferred role
- Networking Core: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
- Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/sock_diag.hlinux/vm_sockets_diag.hnet/af_vsock.h
Detected Declarations
function sock_diagfunction vsock_diag_dumpfunction list_for_each_entryfunction list_for_each_entryfunction vsock_diag_handler_dumpfunction vsock_diag_initfunction vsock_diag_exitmodule init vsock_diag_init
Annotated Snippet
module_init(vsock_diag_init);
module_exit(vsock_diag_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("VMware Virtual Sockets monitoring via SOCK_DIAG");
MODULE_ALIAS_NET_PF_PROTO_TYPE(PF_NETLINK, NETLINK_SOCK_DIAG,
40 /* AF_VSOCK */);
Annotation
- Immediate include surface: `linux/module.h`, `linux/sock_diag.h`, `linux/vm_sockets_diag.h`, `net/af_vsock.h`.
- Detected declarations: `function sock_diag`, `function vsock_diag_dump`, `function list_for_each_entry`, `function list_for_each_entry`, `function vsock_diag_handler_dump`, `function vsock_diag_init`, `function vsock_diag_exit`, `module init vsock_diag_init`.
- Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.