net/handshake/genl.h
Source file repositories/reference/linux-study-clean/net/handshake/genl.h
File Facts
- System
- Linux kernel
- Corpus path
net/handshake/genl.h- Extension
.h- Size
- 727 bytes
- Lines
- 27
- Domain
- Networking Core
- Bucket
- Sockets, Protocols, Packet Path, And Network Policy
- Inferred role
- Networking Core: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
net/netlink.hnet/genetlink.huapi/linux/handshake.hlinux/err.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _LINUX_HANDSHAKE_GEN_H
#define _LINUX_HANDSHAKE_GEN_H
#include <net/netlink.h>
#include <net/genetlink.h>
#include <uapi/linux/handshake.h>
#include <linux/err.h>
int handshake_nl_accept_doit(struct sk_buff *skb, struct genl_info *info);
int handshake_nl_done_doit(struct sk_buff *skb, struct genl_info *info);
enum {
HANDSHAKE_NLGRP_NONE,
HANDSHAKE_NLGRP_TLSHD,
};
extern struct genl_family handshake_nl_family;
#endif /* _LINUX_HANDSHAKE_GEN_H */
Annotation
- Immediate include surface: `net/netlink.h`, `net/genetlink.h`, `uapi/linux/handshake.h`, `linux/err.h`.
- Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
- 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.