net/tipc/core.c

File Facts

System

Linux kernel

Corpus path

net/tipc/core.c

Extension

.c

Size

6035 bytes

Lines

230

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

• core.h
• name_table.h
• subscr.h
• bearer.h
• net.h
• socket.h
• bcast.h
• node.h
• crypto.h
• linux/module.h

Detected Declarations

• function tipc_init_net
• function tipc_exit_net
• function tipc_pernet_pre_exit
• function tipc_init
• function tipc_exit
• module init tipc_init

Annotated Snippet

module_init(tipc_init);
module_exit(tipc_exit);

MODULE_DESCRIPTION("TIPC: Transparent Inter Process Communication");
MODULE_LICENSE("Dual BSD/GPL");
MODULE_VERSION(TIPC_MOD_VER);

Annotation

• Immediate include surface: `core.h`, `name_table.h`, `subscr.h`, `bearer.h`, `net.h`, `socket.h`, `bcast.h`, `node.h`.
• Detected declarations: `function tipc_init_net`, `function tipc_exit_net`, `function tipc_pernet_pre_exit`, `function tipc_init`, `function tipc_exit`, `module init tipc_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.