lib/test_bitops.c

File Facts

System

Linux kernel

Corpus path

lib/test_bitops.c

Extension

.c

Size

3123 bytes

Lines

140

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.

Dependency Surface

• linux/cleanup.h
• linux/init.h
• linux/module.h
• linux/printk.h
• linux/slab.h

Detected Declarations

• enum bitops_fun
• function test_fns
• function test_bitops_startup
• function test_bitops_unstartup
• module init test_bitops_startup

Annotated Snippet

module_init(test_bitops_startup);
module_exit(test_bitops_unstartup);

MODULE_AUTHOR("Jesse Brandeburg <jesse.brandeburg@intel.com>, Wei Yang <richard.weiyang@gmail.com>");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Bit testing module");

Annotation

• Immediate include surface: `linux/cleanup.h`, `linux/init.h`, `linux/module.h`, `linux/printk.h`, `linux/slab.h`.
• Detected declarations: `enum bitops_fun`, `function test_fns`, `function test_bitops_startup`, `function test_bitops_unstartup`, `module init test_bitops_startup`.
• 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.