samples/connector/cn_test.c

File Facts

System

Linux kernel

Corpus path

samples/connector/cn_test.c

Extension

.c

Size

3946 bytes

Lines

189

Domain

Support Tooling And Documentation

Bucket

samples

Inferred role

Support Tooling And Documentation: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/module.h
• linux/moduleparam.h
• linux/skbuff.h
• linux/slab.h
• linux/timer.h
• linux/connector.h

Detected Declarations

• function cn_test_callback
• function cn_test_want_notify
• function cn_test_timer_func
• function cn_test_init
• function cn_test_fini
• module init cn_test_init

Annotated Snippet

module_init(cn_test_init);
module_exit(cn_test_fini);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Evgeniy Polyakov <zbr@ioremap.net>");
MODULE_DESCRIPTION("Connector's test module");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/skbuff.h`, `linux/slab.h`, `linux/timer.h`, `linux/connector.h`.
• Detected declarations: `function cn_test_callback`, `function cn_test_want_notify`, `function cn_test_timer_func`, `function cn_test_init`, `function cn_test_fini`, `module init cn_test_init`.
• Atlas domain: Support Tooling And Documentation / samples.
• 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.