net/bridge/netfilter/ebtable_nat.c
Source file repositories/reference/linux-study-clean/net/bridge/netfilter/ebtable_nat.c
File Facts
- System
- Linux kernel
- Corpus path
net/bridge/netfilter/ebtable_nat.c- Extension
.c- Size
- 2487 bytes
- Lines
- 118
- 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/netfilter_bridge/ebtables.huapi/linux/netfilter_bridge.hlinux/module.h
Detected Declarations
function frame_nat_table_initfunction frame_nat_net_pre_exitfunction frame_nat_net_exitfunction ebtable_nat_initfunction ebtable_nat_finimodule init ebtable_nat_init
Annotated Snippet
module_init(ebtable_nat_init);
module_exit(ebtable_nat_fini);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("ebtables legacy stateless nat table");Annotation
- Immediate include surface: `linux/netfilter_bridge/ebtables.h`, `uapi/linux/netfilter_bridge.h`, `linux/module.h`.
- Detected declarations: `function frame_nat_table_init`, `function frame_nat_net_pre_exit`, `function frame_nat_net_exit`, `function ebtable_nat_init`, `function ebtable_nat_fini`, `module init ebtable_nat_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.