drivers/net/wireguard/main.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireguard/main.c

Extension

.c

Size

1659 bytes

Lines

79

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.

Dependency Surface

• version.h
• device.h
• noise.h
• queueing.h
• ratelimiter.h
• netlink.h
• uapi/linux/wireguard.h
• linux/init.h
• linux/module.h
• net/genetlink.h
• net/rtnetlink.h

Detected Declarations

• function Copyright
• function wg_mod_exit
• module init wg_mod_init

Annotated Snippet

module_init(wg_mod_init);
module_exit(wg_mod_exit);
MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("WireGuard secure network tunnel");
MODULE_AUTHOR("Jason A. Donenfeld <Jason@zx2c4.com>");
MODULE_VERSION(WIREGUARD_VERSION);
MODULE_ALIAS_RTNL_LINK(KBUILD_MODNAME);
MODULE_ALIAS_GENL_FAMILY(WG_GENL_NAME);

Annotation

• Immediate include surface: `version.h`, `device.h`, `noise.h`, `queueing.h`, `ratelimiter.h`, `netlink.h`, `uapi/linux/wireguard.h`, `linux/init.h`.
• Detected declarations: `function Copyright`, `function wg_mod_exit`, `module init wg_mod_init`.
• Atlas domain: Driver Families / drivers/net.
• 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.