net/bridge/netfilter/ebt_snat.c
Source file repositories/reference/linux-study-clean/net/bridge/netfilter/ebt_snat.c
File Facts
- System
- Linux kernel
- Corpus path
net/bridge/netfilter/ebt_snat.c- Extension
.c- Size
- 2154 bytes
- Lines
- 92
- 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.hnet/sock.hlinux/if_arp.hnet/arp.hlinux/netfilter.hlinux/netfilter/x_tables.hlinux/netfilter_bridge/ebtables.hlinux/netfilter_bridge/ebt_nat.h
Detected Declarations
function ebt_snat_tgfunction eth_hdrfunction ebt_snat_tg_checkfunction ebt_snat_initfunction ebt_snat_finimodule init ebt_snat_init
Annotated Snippet
module_init(ebt_snat_init);
module_exit(ebt_snat_fini);
MODULE_DESCRIPTION("Ebtables: Source MAC address translation");
MODULE_LICENSE("GPL");Annotation
- Immediate include surface: `linux/module.h`, `net/sock.h`, `linux/if_arp.h`, `net/arp.h`, `linux/netfilter.h`, `linux/netfilter/x_tables.h`, `linux/netfilter_bridge/ebtables.h`, `linux/netfilter_bridge/ebt_nat.h`.
- Detected declarations: `function ebt_snat_tg`, `function eth_hdr`, `function ebt_snat_tg_check`, `function ebt_snat_init`, `function ebt_snat_fini`, `module init ebt_snat_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.