drivers/net/wireguard/generated/netlink.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireguard/generated/netlink.h

Extension

.h

Size

1061 bytes

Lines

31

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: implementation source

Status

source 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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• net/netlink.h
• net/genetlink.h
• uapi/linux/wireguard.h
• linux/time_types.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _LINUX_WIREGUARD_GEN_H
#define _LINUX_WIREGUARD_GEN_H

#include <net/netlink.h>
#include <net/genetlink.h>

#include <uapi/linux/wireguard.h>
#include <linux/time_types.h>

/* Common nested types */
extern const struct nla_policy wireguard_wgallowedip_nl_policy[WGALLOWEDIP_A_FLAGS + 1];
extern const struct nla_policy wireguard_wgpeer_nl_policy[WGPEER_A_PROTOCOL_VERSION + 1];

/* Ops table for wireguard */
extern const struct genl_split_ops wireguard_nl_ops[2];

int wg_get_device_start(struct netlink_callback *cb);
int wg_get_device_done(struct netlink_callback *cb);

int wg_get_device_dumpit(struct sk_buff *skb, struct netlink_callback *cb);
int wg_set_device_doit(struct sk_buff *skb, struct genl_info *info);

#endif /* _LINUX_WIREGUARD_GEN_H */

Annotation

• Immediate include surface: `net/netlink.h`, `net/genetlink.h`, `uapi/linux/wireguard.h`, `linux/time_types.h`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source 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.