include/net/ipcomp.h
Source file repositories/reference/linux-study-clean/include/net/ipcomp.h
File Facts
- System
- Linux kernel
- Corpus path
include/net/ipcomp.h- Extension
.h- Size
- 561 bytes
- Lines
- 22
- Domain
- Networking Core
- Bucket
- Sockets, Protocols, Packet Path, And Network Policy
- Inferred role
- Networking Core: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/skbuff.h
Detected Declarations
struct ip_comp_hdrstruct netlink_ext_ackstruct xfrm_state
Annotated Snippet
#ifndef _NET_IPCOMP_H
#define _NET_IPCOMP_H
#include <linux/skbuff.h>
struct ip_comp_hdr;
struct netlink_ext_ack;
struct xfrm_state;
int ipcomp_input(struct xfrm_state *x, struct sk_buff *skb);
int ipcomp_output(struct xfrm_state *x, struct sk_buff *skb);
void ipcomp_destroy(struct xfrm_state *x);
int ipcomp_init_state(struct xfrm_state *x, struct netlink_ext_ack *extack);
static inline struct ip_comp_hdr *ip_comp_hdr(const struct sk_buff *skb)
{
return (struct ip_comp_hdr *)skb_transport_header(skb);
}
#endif
Annotation
- Immediate include surface: `linux/skbuff.h`.
- Detected declarations: `struct ip_comp_hdr`, `struct netlink_ext_ack`, `struct xfrm_state`.
- Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
- Implementation status: source 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.