net/core/lock_debug.c
Source file repositories/reference/linux-study-clean/net/core/lock_debug.c
File Facts
- System
- Linux kernel
- Corpus path
net/core/lock_debug.c- Extension
.c- Size
- 3110 bytes
- Lines
- 124
- 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/init.hlinux/netdevice.hlinux/notifier.hlinux/rtnetlink.hnet/net_namespace.hnet/netdev_lock.hnet/netns/generic.h
Detected Declarations
function netdev_debug_eventfunction rtnl_net_debug_net_initfunction rtnl_net_debug_net_exitfunction rtnl_net_debug_initmodule init rtnl_net_debug_init
Annotated Snippet
subsys_initcall(rtnl_net_debug_init);Annotation
- Immediate include surface: `linux/init.h`, `linux/netdevice.h`, `linux/notifier.h`, `linux/rtnetlink.h`, `net/net_namespace.h`, `net/netdev_lock.h`, `net/netns/generic.h`.
- Detected declarations: `function netdev_debug_event`, `function rtnl_net_debug_net_init`, `function rtnl_net_debug_net_exit`, `function rtnl_net_debug_init`, `module init rtnl_net_debug_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.