net/netfilter/nf_flow_table_core.c

File Facts

System

Linux kernel

Corpus path

net/netfilter/nf_flow_table_core.c

Extension

.c

Size

22709 bytes

Lines

857

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/init.h
• linux/module.h
• linux/netfilter.h
• linux/rhashtable.h
• linux/netdevice.h
• net/ip.h
• net/ip6_route.h
• net/netfilter/nf_tables.h
• net/netfilter/nf_flow_table.h
• net/netfilter/nf_conntrack.h
• net/netfilter/nf_conntrack_core.h
• net/netfilter/nf_conntrack_l4proto.h
• net/netfilter/nf_conntrack_tuple.h

Detected Declarations

• function flow_offload_fill_dir
• function flow_offload_dst_cookie
• function flow_offload_fill_route
• function nft_flow_dst_release
• function flow_offload_route_init
• function nf_flow_has_expired
• function flow_offload_fixup_tcp
• function flow_offload_fixup_ct
• function flow_offload_route_release
• function flow_offload_free
• function flow_offload_hash
• function flow_offload_hash_obj
• function flow_offload_hash_cmp
• function flow_offload_get_timeout
• function flow_offload_add
• function flow_offload_refresh
• function flow_offload_del
• function flow_offload_teardown
• function flow_offload_lookup
• function nf_flow_table_iterate
• function nf_flow_custom_gc
• function nf_flow_table_tcp_timeout
• function nf_flow_table_extend_ct_timeout
• function nf_flow_offload_gc_step
• function test_bit
• function nf_flow_table_gc_run
• function nf_flow_offload_work_gc
• function nf_flow_nat_port_tcp
• function nf_flow_nat_port_udp
• function nf_flow_nat_port
• function nf_flow_snat_port
• function nf_flow_dnat_port
• function nf_flow_table_init
• function nf_flow_table_do_cleanup
• function nf_flow_table_gc_cleanup
• function nf_flow_table_cleanup
• function nf_flow_table_free
• function nf_flow_table_init_net
• function nf_flow_table_fini_net
• function nf_flow_table_pernet_init
• function nf_flow_table_pernet_exit
• function list_for_each_entry
• function nf_flow_table_module_init
• function nf_flow_table_module_exit
• module init nf_flow_table_module_init
• export flow_offload_alloc
• export flow_offload_route_init
• export flow_offload_free

Annotated Snippet

module_init(nf_flow_table_module_init);
module_exit(nf_flow_table_module_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Pablo Neira Ayuso <pablo@netfilter.org>");
MODULE_DESCRIPTION("Netfilter flow table module");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/module.h`, `linux/netfilter.h`, `linux/rhashtable.h`, `linux/netdevice.h`, `net/ip.h`, `net/ip6_route.h`.
• Detected declarations: `function flow_offload_fill_dir`, `function flow_offload_dst_cookie`, `function flow_offload_fill_route`, `function nft_flow_dst_release`, `function flow_offload_route_init`, `function nf_flow_has_expired`, `function flow_offload_fixup_tcp`, `function flow_offload_fixup_ct`, `function flow_offload_route_release`, `function flow_offload_free`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.