include/net/inet6_connection_sock.h

File Facts

System

Linux kernel

Corpus path

include/net/inet6_connection_sock.h

Extension

.h

Size

784 bytes

Lines

32

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

• linux/types.h

Detected Declarations

• struct flowi
• struct flowi6
• struct request_sock
• struct sk_buff
• struct sock
• struct sockaddr

Annotated Snippet

#ifndef _INET6_CONNECTION_SOCK_H
#define _INET6_CONNECTION_SOCK_H

#include <linux/types.h>

struct flowi;
struct flowi6;
struct request_sock;
struct sk_buff;
struct sock;
struct sockaddr;

struct dst_entry *inet6_csk_route_socket(struct sock *sk,
					 struct flowi6 *fl6);

struct dst_entry *inet6_csk_route_req(const struct sock *sk,
				      struct dst_entry *dst,
				      struct flowi6 *fl6,
				      const struct request_sock *req, u8 proto);

int inet6_csk_xmit(struct sock *sk, struct sk_buff *skb, struct flowi *fl);

#endif /* _INET6_CONNECTION_SOCK_H */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct flowi`, `struct flowi6`, `struct request_sock`, `struct sk_buff`, `struct sock`, `struct sockaddr`.
• 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.