net/nsh/nsh.c

File Facts

System

Linux kernel

Corpus path

net/nsh/nsh.c

Extension

.c

Size

3350 bytes

Lines

154

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/netdevice.h
• linux/skbuff.h
• net/gso.h
• net/nsh.h
• net/tun_proto.h

Detected Declarations

• function Copyright
• function nsh_pop
• function nsh_init_module
• function nsh_cleanup_module
• module init nsh_init_module
• export nsh_push
• export nsh_pop

Annotated Snippet

module_init(nsh_init_module);
module_exit(nsh_cleanup_module);

MODULE_AUTHOR("Jiri Benc <jbenc@redhat.com>");
MODULE_DESCRIPTION("NSH protocol");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/module.h`, `linux/netdevice.h`, `linux/skbuff.h`, `net/gso.h`, `net/nsh.h`, `net/tun_proto.h`.
• Detected declarations: `function Copyright`, `function nsh_pop`, `function nsh_init_module`, `function nsh_cleanup_module`, `module init nsh_init_module`, `export nsh_push`, `export nsh_pop`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration 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.