net/ipv4/netfilter/ipt_rpfilter.c
Source file repositories/reference/linux-study-clean/net/ipv4/netfilter/ipt_rpfilter.c
File Facts
- System
- Linux kernel
- Corpus path
net/ipv4/netfilter/ipt_rpfilter.c- Extension
.c- Size
- 3407 bytes
- Lines
- 128
- 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/netdevice.hlinux/ip.hnet/flow.hnet/ip.hnet/ip_fib.hnet/route.hlinux/netfilter/xt_rpfilter.hlinux/netfilter/x_tables.h
Detected Declarations
function rpfilter_get_saddrfunction rpfilter_lookup_reversefunction rpfilter_is_loopbackfunction rpfilter_mtfunction rpfilter_checkfunction rpfilter_mt_initfunction rpfilter_mt_exitmodule init rpfilter_mt_init
Annotated Snippet
module_init(rpfilter_mt_init);
module_exit(rpfilter_mt_exit);Annotation
- Immediate include surface: `linux/module.h`, `linux/skbuff.h`, `linux/netdevice.h`, `linux/ip.h`, `net/flow.h`, `net/ip.h`, `net/ip_fib.h`, `net/route.h`.
- Detected declarations: `function rpfilter_get_saddr`, `function rpfilter_lookup_reverse`, `function rpfilter_is_loopback`, `function rpfilter_mt`, `function rpfilter_check`, `function rpfilter_mt_init`, `function rpfilter_mt_exit`, `module init rpfilter_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.