net/ipv4/nexthop.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/nexthop.c

Extension

.c

Size

103554 bytes

Lines

4204

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/nexthop.h
• linux/rtnetlink.h
• linux/slab.h
• linux/vmalloc.h
• net/arp.h
• net/ip6_route.h
• net/lwtunnel.h
• net/ndisc.h
• net/nexthop.h
• net/route.h
• net/sock.h

Detected Declarations

• struct nh_dump_filter
• struct rtm_dump_nh_ctx
• struct rtm_dump_res_bucket_ctx
• struct rtm_dump_nexthop_bucket_data
• function nexthop_notifiers_is_empty
• function __nh_notifier_single_info_init
• function nh_notifier_single_info_init
• function nh_notifier_single_info_fini
• function nh_notifier_mpath_info_init
• function nh_notifier_res_table_info_init
• function nh_notifier_grp_info_init
• function nh_notifier_grp_info_fini
• function nh_notifier_info_init
• function nh_notifier_info_fini
• function call_nexthop_notifiers
• function nh_notifier_res_bucket_idle_timer_get
• function nh_notifier_res_bucket_info_init
• function nh_notifier_res_bucket_info_fini
• function __call_nexthop_res_bucket_notifiers
• function rtnl_dereference
• function call_nexthop_res_table_notifiers
• function call_nexthop_notifier
• function nh_dev_hashfn
• function nexthop_devhash_add
• function nexthop_free_group
• function nexthop_free_single
• function nexthop_free_rcu
• function nexthop_res_table_alloc
• function nh_base_seq_inc
• function nh_find_unused_id
• function nh_res_time_set_deadline
• function nh_res_table_unbalanced_time
• function nla_put_nh_group_res
• function nh_grp_entry_stats_inc
• function nh_grp_entry_stats_read
• function for_each_possible_cpu
• function nh_notifier_grp_hw_stats_init
• function nh_notifier_grp_hw_stats_fini
• function nh_grp_hw_stats_report_delta
• function nh_grp_hw_stats_apply_update
• function nh_grp_hw_stats_update
• function nla_put_nh_group_stats_entry
• function nla_put_nh_group_stats
• function nla_put_nh_group
• function nh_fill_node
• function nh_nlmsg_size_grp_res
• function nh_nlmsg_size_grp
• function nh_nlmsg_size_single

Annotated Snippet

subsys_initcall(nexthop_init);

Annotation

• Immediate include surface: `linux/nexthop.h`, `linux/rtnetlink.h`, `linux/slab.h`, `linux/vmalloc.h`, `net/arp.h`, `net/ip6_route.h`, `net/lwtunnel.h`, `net/ndisc.h`.
• Detected declarations: `struct nh_dump_filter`, `struct rtm_dump_nh_ctx`, `struct rtm_dump_res_bucket_ctx`, `struct rtm_dump_nexthop_bucket_data`, `function nexthop_notifiers_is_empty`, `function __nh_notifier_single_info_init`, `function nh_notifier_single_info_init`, `function nh_notifier_single_info_fini`, `function nh_notifier_mpath_info_init`, `function nh_notifier_res_table_info_init`.
• 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.