lib/test_ref_tracker.c

File Facts

System

Linux kernel

Corpus path

lib/test_ref_tracker.c

Extension

.c

Size

3189 bytes

Lines

117

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

• Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/module.h
• linux/delay.h
• linux/ref_tracker.h
• linux/slab.h
• linux/timer.h

Detected Declarations

• function alloctest_ref_tracker_free
• function test_ref_tracker_timer_func
• function test_ref_tracker_init
• function test_ref_tracker_exit
• module init test_ref_tracker_init

Annotated Snippet

module_init(test_ref_tracker_init);
module_exit(test_ref_tracker_exit);

MODULE_DESCRIPTION("Reference tracker self test");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/init.h`, `linux/module.h`, `linux/delay.h`, `linux/ref_tracker.h`, `linux/slab.h`, `linux/timer.h`.
• Detected declarations: `function alloctest_ref_tracker_free`, `function test_ref_tracker_timer_func`, `function test_ref_tracker_init`, `function test_ref_tracker_exit`, `module init test_ref_tracker_init`.
• Atlas domain: Kernel Services / lib.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.