net/ipv6/netfilter/ip6table_mangle.c
Source file repositories/reference/linux-study-clean/net/ipv6/netfilter/ip6table_mangle.c
File Facts
- System
- Linux kernel
- Corpus path
net/ipv6/netfilter/ip6table_mangle.c- Extension
.c- Size
- 3711 bytes
- Lines
- 139
- 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/module.hlinux/netfilter_ipv6/ip6_tables.hlinux/slab.hnet/ipv6.h
Detected Declarations
function ip6t_mangle_outfunction ip6table_mangle_hookfunction ip6table_mangle_table_initfunction ip6table_mangle_net_pre_exitfunction ip6table_mangle_net_exitfunction ip6table_mangle_initfunction ip6table_mangle_finimodule init ip6table_mangle_init
Annotated Snippet
module_init(ip6table_mangle_init);
module_exit(ip6table_mangle_fini);Annotation
- Immediate include surface: `linux/module.h`, `linux/netfilter_ipv6/ip6_tables.h`, `linux/slab.h`, `net/ipv6.h`.
- Detected declarations: `function ip6t_mangle_out`, `function ip6table_mangle_hook`, `function ip6table_mangle_table_init`, `function ip6table_mangle_net_pre_exit`, `function ip6table_mangle_net_exit`, `function ip6table_mangle_init`, `function ip6table_mangle_fini`, `module init ip6table_mangle_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.