tools/testing/selftests/livepatch/test_modules/test_klp_livepatch.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/livepatch/test_modules/test_klp_livepatch.c

Extension

.c

Size

1090 bytes

Lines

52

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• 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/kernel.h
• linux/livepatch.h
• linux/seq_file.h

Detected Declarations

• function livepatch_cmdline_proc_show
• function test_klp_livepatch_init
• function test_klp_livepatch_exit
• module init test_klp_livepatch_init

Annotated Snippet

module_init(test_klp_livepatch_init);
module_exit(test_klp_livepatch_exit);
MODULE_LICENSE("GPL");
MODULE_INFO(livepatch, "Y");
MODULE_AUTHOR("Seth Jennings <sjenning@redhat.com>");
MODULE_DESCRIPTION("Livepatch test: livepatch module");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/livepatch.h`, `linux/seq_file.h`.
• Detected declarations: `function livepatch_cmdline_proc_show`, `function test_klp_livepatch_init`, `function test_klp_livepatch_exit`, `module init test_klp_livepatch_init`.
• Atlas domain: Support Tooling And Documentation / tools.
• 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.