net/ipv4/inet_diag.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/inet_diag.c

Extension

.c

Size

27907 bytes

Lines

1125

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/kernel.h
• linux/module.h
• linux/types.h
• linux/fcntl.h
• linux/random.h
• linux/slab.h
• linux/cache.h
• linux/init.h
• linux/time.h
• net/icmp.h
• net/tcp.h
• net/ipv6.h
• net/inet_common.h
• net/inet_connection_sock.h
• net/bpf_sk_storage.h
• net/netlink.h
• linux/inet.h
• linux/stddef.h
• linux/inet_diag.h
• linux/sock_diag.h

Detected Declarations

• struct inet_diag_entry
• function inet_diag_unlock_handler
• function inet_diag_msg_common_fill
• function inet_diag_msg_attrs_fill
• function inet_diag_parse_attrs
• function nlmsg_for_each_attr
• function inet_diag_get_protocol
• function inet_sk_diag_fill
• function timer_pending
• function inet_diag_cmd_exact
• function bitstring_match
• function inet_diag_bc_run
• function entry_fill_addrs
• function inet_diag_bc_sk
• function valid_cc
• function valid_devcond
• function valid_hostcond
• function valid_port_comparison
• function valid_markcond
• function valid_cgroupcond
• function inet_diag_bc_audit
• function __inet_diag_dump
• function inet_sk_diag_fill
• function inet_diag_dump
• function __inet_diag_dump_start
• function inet_diag_dump_start
• function inet_diag_dump_start_compat
• function inet_diag_dump_done
• function inet_diag_type2proto
• function inet_diag_dump_compat
• function inet_diag_get_exact_compat
• function inet_diag_rcv_msg_compat
• function inet_diag_handler_cmd
• function inet_diag_handler_get_info
• function inet_diag_register
• function inet_diag_unregister
• function inet_diag_init
• function inet_diag_exit
• module init inet_diag_init
• export inet_diag_msg_common_fill
• export inet_diag_msg_attrs_fill
• export inet_sk_diag_fill
• export inet_diag_bc_sk
• export inet_diag_register
• export inet_diag_unregister

Annotated Snippet

module_init(inet_diag_init);
module_exit(inet_diag_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("INET/INET6: socket monitoring via SOCK_DIAG");
MODULE_ALIAS_NET_PF_PROTO_TYPE(PF_NETLINK, NETLINK_SOCK_DIAG, 2 /* AF_INET */);
MODULE_ALIAS_NET_PF_PROTO_TYPE(PF_NETLINK, NETLINK_SOCK_DIAG, 10 /* AF_INET6 */);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/types.h`, `linux/fcntl.h`, `linux/random.h`, `linux/slab.h`, `linux/cache.h`, `linux/init.h`.
• Detected declarations: `struct inet_diag_entry`, `function inet_diag_unlock_handler`, `function inet_diag_msg_common_fill`, `function inet_diag_msg_attrs_fill`, `function inet_diag_parse_attrs`, `function nlmsg_for_each_attr`, `function inet_diag_get_protocol`, `function inet_sk_diag_fill`, `function timer_pending`, `function inet_diag_cmd_exact`.
• 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.