net/core/net-sysfs.h

File Facts

System

Linux kernel

Corpus path

net/core/net-sysfs.h

Extension

.h

Size

604 bytes

Lines

18

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

• No C-style include directives detected by the generator.

Detected Declarations

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

Annotated Snippet

#ifndef __NET_SYSFS_H__
#define __NET_SYSFS_H__

int __init netdev_kobject_init(void);
int netdev_register_kobject(struct net_device *);
void netdev_unregister_kobject(struct net_device *);
int net_rx_queue_update_kobjects(struct net_device *, int old_num, int new_num);
int netdev_queue_update_kobjects(struct net_device *net,
				 int old_num, int new_num);
int netdev_change_owner(struct net_device *, const struct net *net_old,
			const struct net *net_new);

extern struct mutex rps_default_mask_mutex;

DECLARE_STATIC_KEY_FALSE(skb_defer_disable_key);
#endif

Annotation

• 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.