net/ipv6/netfilter/ip6t_frag.c
Source file repositories/reference/linux-study-clean/net/ipv6/netfilter/ip6t_frag.c
File Facts
- System
- Linux kernel
- Corpus path
net/ipv6/netfilter/ip6t_frag.c- Extension
.c- Size
- 3816 bytes
- Lines
- 133
- 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/skbuff.hlinux/ipv6.hlinux/types.hnet/checksum.hnet/ipv6.hlinux/netfilter/x_tables.hlinux/netfilter_ipv6/ip6_tables.hlinux/netfilter_ipv6/ip6t_frag.h
Detected Declarations
function id_matchfunction frag_mt6function frag_mt6_checkfunction frag_mt6_initfunction frag_mt6_exitmodule init frag_mt6_init
Annotated Snippet
module_init(frag_mt6_init);
module_exit(frag_mt6_exit);Annotation
- Immediate include surface: `linux/module.h`, `linux/skbuff.h`, `linux/ipv6.h`, `linux/types.h`, `net/checksum.h`, `net/ipv6.h`, `linux/netfilter/x_tables.h`, `linux/netfilter_ipv6/ip6_tables.h`.
- Detected declarations: `function id_match`, `function frag_mt6`, `function frag_mt6_check`, `function frag_mt6_init`, `function frag_mt6_exit`, `module init frag_mt6_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.