lib/test_static_keys.c

File Facts

System

Linux kernel

Corpus path

lib/test_static_keys.c

Extension

.c

Size

5792 bytes

Lines

241

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
• linux/jump_label.h

Detected Declarations

• struct test_key
• function invert_key
• function invert_keys
• function verify_keys
• function test_static_key_init
• function test_static_key_exit
• module init test_static_key_init

Annotated Snippet

module_init(test_static_key_init);
module_exit(test_static_key_exit);

MODULE_AUTHOR("Jason Baron <jbaron@akamai.com>");
MODULE_DESCRIPTION("Kernel module for testing static keys");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/jump_label.h`.
• Detected declarations: `struct test_key`, `function invert_key`, `function invert_keys`, `function verify_keys`, `function test_static_key_init`, `function test_static_key_exit`, `module init test_static_key_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.