net/ipv4/netfilter/ipt_SYNPROXY.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/netfilter/ipt_SYNPROXY.c

Extension

.c

Size

3111 bytes

Lines

122

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_ipv4/ip_tables.h
• linux/netfilter/x_tables.h
• linux/netfilter/xt_SYNPROXY.h
• net/netfilter/nf_synproxy.h

Detected Declarations

• function Copyright
• function synproxy_tg4_check
• function synproxy_tg4_destroy
• function synproxy_tg4_init
• function synproxy_tg4_exit
• module init synproxy_tg4_init

Annotated Snippet

module_init(synproxy_tg4_init);
module_exit(synproxy_tg4_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Patrick McHardy <kaber@trash.net>");
MODULE_DESCRIPTION("Intercept TCP connections and establish them using syncookies");

Annotation

• Immediate include surface: `linux/netfilter_ipv4/ip_tables.h`, `linux/netfilter/x_tables.h`, `linux/netfilter/xt_SYNPROXY.h`, `net/netfilter/nf_synproxy.h`.
• Detected declarations: `function Copyright`, `function synproxy_tg4_check`, `function synproxy_tg4_destroy`, `function synproxy_tg4_init`, `function synproxy_tg4_exit`, `module init synproxy_tg4_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.