lib/test_dynamic_debug.c

File Facts

System

Linux kernel

Corpus path

lib/test_dynamic_debug.c

Extension

.c

Size

3826 bytes

Lines

167

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h

Detected Declarations

• enum cat_disjoint_bits
• enum cat_disjoint_names
• enum cat_level_num
• enum cat_level_names
• function param_set_do_prints
• function param_get_do_prints
• function do_cats
• function do_levels
• function do_prints
• function test_dynamic_debug_init
• function test_dynamic_debug_exit
• module init test_dynamic_debug_init

Annotated Snippet

module_init(test_dynamic_debug_init);
module_exit(test_dynamic_debug_exit);

MODULE_AUTHOR("Jim Cromie <jim.cromie@gmail.com>");
MODULE_DESCRIPTION("Kernel module for testing dynamic_debug");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`.
• Detected declarations: `enum cat_disjoint_bits`, `enum cat_disjoint_names`, `enum cat_level_num`, `enum cat_level_names`, `function param_set_do_prints`, `function param_get_do_prints`, `function do_cats`, `function do_levels`, `function do_prints`, `function test_dynamic_debug_init`.
• Atlas domain: Kernel Services / lib.
• 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.