net/tipc/diag.c

File Facts

System

Linux kernel

Corpus path

net/tipc/diag.c

Extension

.c

Size

3675 bytes

Lines

119

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• core.h
• socket.h
• linux/sock_diag.h
• linux/tipc_sockets_diag.h

Detected Declarations

• function __tipc_diag_gen_cookie
• function __tipc_add_sock_diag
• function tipc_diag_dump
• function tipc_sock_diag_handler_dump
• function tipc_diag_init
• function tipc_diag_exit
• module init tipc_diag_init

Annotated Snippet

module_init(tipc_diag_init);
module_exit(tipc_diag_exit);

MODULE_LICENSE("Dual BSD/GPL");
MODULE_DESCRIPTION("TIPC socket monitoring via SOCK_DIAG");
MODULE_ALIAS_NET_PF_PROTO_TYPE(PF_NETLINK, NETLINK_SOCK_DIAG, AF_TIPC);

Annotation

• Immediate include surface: `core.h`, `socket.h`, `linux/sock_diag.h`, `linux/tipc_sockets_diag.h`.
• Detected declarations: `function __tipc_diag_gen_cookie`, `function __tipc_add_sock_diag`, `function tipc_diag_dump`, `function tipc_sock_diag_handler_dump`, `function tipc_diag_init`, `function tipc_diag_exit`, `module init tipc_diag_init`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration 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.