net/netfilter/xt_policy.c
Source file repositories/reference/linux-study-clean/net/netfilter/xt_policy.c
File Facts
- System
- Linux kernel
- Corpus path
net/netfilter/xt_policy.c- Extension
.c- Size
- 5071 bytes
- Lines
- 204
- 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/kernel.hlinux/module.hlinux/skbuff.hlinux/init.hnet/xfrm.hlinux/netfilter.hlinux/netfilter/xt_policy.hlinux/netfilter/x_tables.h
Detected Declarations
function xt_addr_cmpfunction match_xfrm_statefunction match_policy_infunction match_policy_outfunction policy_mtfunction policy_mt_check_hooksfunction policy_mt_checkfunction policy_mt_initfunction policy_mt_exitmodule init policy_mt_init
Annotated Snippet
module_init(policy_mt_init);
module_exit(policy_mt_exit);
MODULE_ALIAS("ipt_policy");
MODULE_ALIAS("ip6t_policy");
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/skbuff.h`, `linux/init.h`, `net/xfrm.h`, `linux/netfilter.h`, `linux/netfilter/xt_policy.h`, `linux/netfilter/x_tables.h`.
- Detected declarations: `function xt_addr_cmp`, `function match_xfrm_state`, `function match_policy_in`, `function match_policy_out`, `function policy_mt`, `function policy_mt_check_hooks`, `function policy_mt_check`, `function policy_mt_init`, `function policy_mt_exit`, `module init policy_mt_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.