net/xfrm/xfrm_user.c

File Facts

System

Linux kernel

Corpus path

net/xfrm/xfrm_user.c

Extension

.c

Size

115287 bytes

Lines

4652

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/compat.h
• linux/crypto.h
• linux/module.h
• linux/kernel.h
• linux/types.h
• linux/slab.h
• linux/socket.h
• linux/string.h
• linux/net.h
• linux/skbuff.h
• linux/pfkeyv2.h
• linux/ipsec.h
• linux/init.h
• linux/security.h
• net/sock.h
• net/xfrm.h
• net/netlink.h
• net/ah.h
• linux/uaccess.h
• linux/in6.h
• linux/unaligned.h

Detected Declarations

• struct xfrm_dump_info
• function Copyright
• function verify_one_alg
• function verify_auth_trunc
• function verify_aead
• function verify_one_addr
• function verify_sec_ctx_len
• function verify_replay
• function verify_mtimer_thresh
• function verify_xfrm_family
• function verify_selector_prefixlen
• function verify_newsa_info
• function attach_one_algo
• function attach_crypt
• function attach_auth
• function attach_auth_trunc
• function attach_aead
• function xfrm_replay_verify_len
• function xfrm_alloc_replay_state_esn
• function xfrm_user_sec_ctx_size
• function copy_from_user_state
• function xfrm_update_ae_params
• function xfrm_smark_init
• function xfrm_add_sa
• function xfrm_del_sa
• function copy_to_user_state
• function copy_sec_ctx
• function xso_to_xuo
• function copy_user_offload
• function xfrm_redact
• function copy_to_user_auth
• function copy_to_user_aead
• function copy_to_user_ealg
• function copy_to_user_calg
• function copy_to_user_encap
• function xfrm_smark_put
• function copy_to_user_state_extra
• function dump_one_state
• function xfrm_dump_sa_done
• function xfrm_dump_sa
• function xfrm_nlmsg_multicast
• function xfrm_spdinfo_msgsize
• function build_spdinfo
• function xfrm_set_spdinfo
• function xfrm_get_spdinfo
• function xfrm_sadinfo_msgsize
• function build_sadinfo
• function xfrm_get_sadinfo

Annotated Snippet

module_init(xfrm_user_init);
module_exit(xfrm_user_exit);
MODULE_DESCRIPTION("XFRM User interface");
MODULE_LICENSE("GPL");
MODULE_ALIAS_NET_PF_PROTO(PF_NETLINK, NETLINK_XFRM);

Annotation

• Immediate include surface: `linux/compat.h`, `linux/crypto.h`, `linux/module.h`, `linux/kernel.h`, `linux/types.h`, `linux/slab.h`, `linux/socket.h`, `linux/string.h`.
• Detected declarations: `struct xfrm_dump_info`, `function Copyright`, `function verify_one_alg`, `function verify_auth_trunc`, `function verify_aead`, `function verify_one_addr`, `function verify_sec_ctx_len`, `function verify_replay`, `function verify_mtimer_thresh`, `function verify_xfrm_family`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• 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.