net/netfilter/nf_nat_ftp.c
Source file repositories/reference/linux-study-clean/net/netfilter/nf_nat_ftp.c
File Facts
- System
- Linux kernel
- Corpus path
net/netfilter/nf_nat_ftp.c- Extension
.c- Size
- 3904 bytes
- Lines
- 139
- 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/moduleparam.hlinux/inet.hlinux/tcp.hlinux/netfilter_ipv4.hnet/netfilter/nf_nat.hnet/netfilter/nf_nat_helper.hnet/netfilter/nf_conntrack_helper.hnet/netfilter/nf_conntrack_expect.hlinux/netfilter/nf_conntrack_ftp.h
Detected Declarations
function nf_nat_ftp_fmt_cmdfunction nf_nat_ftpfunction nf_nat_ftp_finifunction nf_nat_ftp_initfunction warn_setmodule init nf_nat_ftp_init
Annotated Snippet
module_init(nf_nat_ftp_init);
module_exit(nf_nat_ftp_fini);Annotation
- Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/inet.h`, `linux/tcp.h`, `linux/netfilter_ipv4.h`, `net/netfilter/nf_nat.h`, `net/netfilter/nf_nat_helper.h`, `net/netfilter/nf_conntrack_helper.h`.
- Detected declarations: `function nf_nat_ftp_fmt_cmd`, `function nf_nat_ftp`, `function nf_nat_ftp_fini`, `function nf_nat_ftp_init`, `function warn_set`, `module init nf_nat_ftp_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.