net/netfilter/ipvs/ip_vs_core.c

File Facts

System

Linux kernel

Corpus path

net/netfilter/ipvs/ip_vs_core.c

Extension

.c

Size

71127 bytes

Lines

2633

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/kernel.h
• linux/ip.h
• linux/tcp.h
• linux/sctp.h
• linux/icmp.h
• linux/slab.h
• net/ip.h
• net/tcp.h
• net/udp.h
• net/icmp.h
• net/gue.h
• net/gre.h
• net/route.h
• net/ip6_checksum.h
• net/netns/generic.h
• linux/netfilter.h
• linux/netfilter_ipv4.h
• net/ipv6.h
• linux/netfilter_ipv6.h
• net/ip6_route.h
• net/ip_vs.h
• linux/indirect_call_wrapper.h

Detected Declarations

• function ip_vs_init_hash_table
• function factor
• function ip_vs_rht_rcu_free
• function ip_vs_rht_desired_size
• function ip_vs_rht_set_thresholds
• function ip_vs_rht_hash_linfo
• function ip_vs_in_stats
• function ip_vs_out_stats
• function ip_vs_conn_stats
• function ip_vs_set_state
• function ip_vs_conn_fill_param_persist
• function ip_vs_sched_persist
• function NF_DROP
• function ip_vs_addr_is_unicast
• function ip_vs_leave
• function ip_vs_addr_is_unicast
• function sysctl_snat_reroute
• function sysctl_nat_icmp_send
• function sysctl_snat_reroute
• function sysctl_nat_icmp_send
• function ip_vs_checksum_complete
• function ip_vs_defrag_user
• function ip_vs_gather_frags
• function ip_vs_route_me_harder
• function ip_vs_nat_icmp
• function ip_vs_nat_icmp_v6
• function handle_response_icmp
• function ip_vs_out_icmp
• function ip_vs_out_icmp_v6
• function is_sctp_abort
• function is_tcp_reset
• function is_new_conn
• function is_new_conn_expected
• function handle_response
• function ip_vs_out_hook
• function ip_vs_try_to_schedule
• function ipvs_udp_decap
• function ipvs_gre_decap
• function ip_vs_in_icmp
• function ip_vs_in_icmp_v6
• function ip_vs_in_hook
• function is_new_conn_expected
• function ip_vs_forward_icmp
• function ip_vs_register_hooks
• function ip_vs_unregister_hooks
• function __ip_vs_init
• function __ip_vs_cleanup_batch
• function __ip_vs_dev_cleanup_batch

Annotated Snippet

module_init(ip_vs_init);
module_exit(ip_vs_cleanup);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("IP Virtual Server");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/ip.h`, `linux/tcp.h`, `linux/sctp.h`, `linux/icmp.h`, `linux/slab.h`, `net/ip.h`.
• Detected declarations: `function ip_vs_init_hash_table`, `function factor`, `function ip_vs_rht_rcu_free`, `function ip_vs_rht_desired_size`, `function ip_vs_rht_set_thresholds`, `function ip_vs_rht_hash_linfo`, `function ip_vs_in_stats`, `function ip_vs_out_stats`, `function ip_vs_conn_stats`, `function ip_vs_set_state`.
• 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.