net/hsr/hsr_main.c
Source file repositories/reference/linux-study-clean/net/hsr/hsr_main.c
File Facts
- System
- Linux kernel
- Corpus path
net/hsr/hsr_main.c- Extension
.c- Size
- 4376 bytes
- Lines
- 188
- 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/netdevice.hnet/rtnetlink.hlinux/rculist.hlinux/timer.hlinux/etherdevice.hhsr_main.hhsr_device.hhsr_netlink.hhsr_framereg.hhsr_slave.h
Detected Declarations
function Authorfunction hsr_netdev_notifyfunction hsr_get_versionfunction hsr_initfunction hsr_exitmodule init hsr_initexport hsr_get_version
Annotated Snippet
module_init(hsr_init);
module_exit(hsr_exit);
MODULE_DESCRIPTION("High-availability Seamless Redundancy (HSR) driver");
MODULE_LICENSE("GPL");Annotation
- Immediate include surface: `linux/netdevice.h`, `net/rtnetlink.h`, `linux/rculist.h`, `linux/timer.h`, `linux/etherdevice.h`, `hsr_main.h`, `hsr_device.h`, `hsr_netlink.h`.
- Detected declarations: `function Author`, `function hsr_netdev_notify`, `function hsr_get_version`, `function hsr_init`, `function hsr_exit`, `module init hsr_init`, `export hsr_get_version`.
- 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.