net/ipv4/xfrm4_tunnel.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/xfrm4_tunnel.c

Extension

.c

Size

2918 bytes

Lines

120

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

• linux/skbuff.h
• linux/module.h
• net/xfrm.h
• net/protocol.h

Detected Declarations

• function Copyright
• function ipip_xfrm_rcv
• function ipip_init_state
• function ipip_destroy
• function xfrm_tunnel_rcv
• function xfrm_tunnel_err
• function ipip_init
• function ipip_fini
• module init ipip_init

Annotated Snippet

module_init(ipip_init);
module_exit(ipip_fini);
MODULE_DESCRIPTION("IPv4 XFRM tunnel driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS_XFRM_TYPE(AF_INET, XFRM_PROTO_IPIP);

Annotation

• Immediate include surface: `linux/skbuff.h`, `linux/module.h`, `net/xfrm.h`, `net/protocol.h`.
• Detected declarations: `function Copyright`, `function ipip_xfrm_rcv`, `function ipip_init_state`, `function ipip_destroy`, `function xfrm_tunnel_rcv`, `function xfrm_tunnel_err`, `function ipip_init`, `function ipip_fini`, `module init ipip_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.