net/handshake/trace.c
Source file repositories/reference/linux-study-clean/net/handshake/trace.c
File Facts
- System
- Linux kernel
- Corpus path
net/handshake/trace.c- Extension
.c- Size
- 449 bytes
- Lines
- 23
- 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.
Dependency Surface
linux/types.hlinux/ipv6.hnet/sock.hnet/inet_sock.hnet/netlink.hnet/genetlink.hhandshake.htrace/events/handshake.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* Trace points for transport security layer handshakes.
*
* Author: Chuck Lever <chuck.lever@oracle.com>
*
* Copyright (c) 2023, Oracle and/or its affiliates.
*/
#include <linux/types.h>
#include <linux/ipv6.h>
#include <net/sock.h>
#include <net/inet_sock.h>
#include <net/netlink.h>
#include <net/genetlink.h>
#include "handshake.h"
#define CREATE_TRACE_POINTS
#include <trace/events/handshake.h>
Annotation
- Immediate include surface: `linux/types.h`, `linux/ipv6.h`, `net/sock.h`, `net/inet_sock.h`, `net/netlink.h`, `net/genetlink.h`, `handshake.h`, `trace/events/handshake.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.