net/ipv4/ipcomp.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/ipcomp.c

Extension

.c

Size

4788 bytes

Lines

207

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.h
• linux/err.h
• linux/rtnetlink.h
• net/ip.h
• net/xfrm.h
• net/icmp.h
• net/ipcomp.h
• net/protocol.h
• net/sock.h

Detected Declarations

• function Protocol
• function ipcomp_tunnel_attach
• function ipcomp4_init_state
• function ipcomp4_rcv_cb
• function ipcomp4_init
• function ipcomp4_fini
• module init ipcomp4_init

Annotated Snippet

module_init(ipcomp4_init);
module_exit(ipcomp4_fini);

MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("IP Payload Compression Protocol (IPComp/IPv4) - RFC3173");
MODULE_AUTHOR("James Morris <jmorris@intercode.com.au>");

MODULE_ALIAS_XFRM_TYPE(AF_INET, XFRM_PROTO_COMP);

Annotation

• Immediate include surface: `linux/module.h`, `linux/err.h`, `linux/rtnetlink.h`, `net/ip.h`, `net/xfrm.h`, `net/icmp.h`, `net/ipcomp.h`, `net/protocol.h`.
• Detected declarations: `function Protocol`, `function ipcomp_tunnel_attach`, `function ipcomp4_init_state`, `function ipcomp4_rcv_cb`, `function ipcomp4_init`, `function ipcomp4_fini`, `module init ipcomp4_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.