lib/test_hexdump.c

File Facts

System

Linux kernel

Corpus path

lib/test_hexdump.c

Extension

.c

Size

6516 bytes

Lines

258

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.

Dependency Surface

• linux/init.h
• linux/kernel.h
• linux/module.h
• linux/random.h
• linux/string.h

Detected Declarations

• function test_hexdump_prepare_test
• function test_hexdump
• function test_hexdump_set
• function test_hexdump_overflow
• function test_hexdump_overflow_set
• function test_hexdump_init
• function test_hexdump_exit
• module init test_hexdump_init

Annotated Snippet

module_init(test_hexdump_init);

static void __exit test_hexdump_exit(void)
{
	/* do nothing */
}
module_exit(test_hexdump_exit);

MODULE_AUTHOR("Andy Shevchenko <andriy.shevchenko@linux.intel.com>");
MODULE_DESCRIPTION("Test cases for lib/hexdump.c module");
MODULE_LICENSE("Dual BSD/GPL");

Annotation

• Immediate include surface: `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/random.h`, `linux/string.h`.
• Detected declarations: `function test_hexdump_prepare_test`, `function test_hexdump`, `function test_hexdump_set`, `function test_hexdump_overflow`, `function test_hexdump_overflow_set`, `function test_hexdump_init`, `function test_hexdump_exit`, `module init test_hexdump_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.