kernel/backtracetest.c

File Facts

System

Linux kernel

Corpus path

kernel/backtracetest.c

Extension

.c

Size

1872 bytes

Lines

80

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

Inferred role

Core OS: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• 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/completion.h
• linux/delay.h
• linux/interrupt.h
• linux/module.h
• linux/sched.h
• linux/stacktrace.h

Detected Declarations

• function backtrace_test_normal
• function backtrace_test_bh_workfn
• function backtrace_test_bh
• function backtrace_test_saved
• function backtrace_test_saved
• function backtrace_regression_test
• function exitf
• module init backtrace_regression_test

Annotated Snippet

module_init(backtrace_regression_test);
module_exit(exitf);
MODULE_DESCRIPTION("Simple stack backtrace regression test module");
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Arjan van de Ven <arjan@linux.intel.com>");

Annotation

• Immediate include surface: `linux/completion.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/module.h`, `linux/sched.h`, `linux/stacktrace.h`.
• Detected declarations: `function backtrace_test_normal`, `function backtrace_test_bh_workfn`, `function backtrace_test_bh`, `function backtrace_test_saved`, `function backtrace_test_saved`, `function backtrace_regression_test`, `function exitf`, `module init backtrace_regression_test`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• 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.