kernel/trace/rv/reactor_panic.c

File Facts

System

Linux kernel

Corpus path

kernel/trace/rv/reactor_panic.c

Extension

.c

Size

1005 bytes

Lines

43

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/ftrace.h
• linux/tracepoint.h
• linux/kernel.h
• linux/module.h
• linux/init.h
• linux/rv.h

Detected Declarations

• function Copyright
• function register_react_panic
• function unregister_react_panic
• module init register_react_panic

Annotated Snippet

module_init(register_react_panic);
module_exit(unregister_react_panic);

MODULE_AUTHOR("Daniel Bristot de Oliveira");
MODULE_DESCRIPTION("panic rv reactor: panic if an exception is found.");

Annotation

• Immediate include surface: `linux/ftrace.h`, `linux/tracepoint.h`, `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/rv.h`.
• Detected declarations: `function Copyright`, `function register_react_panic`, `function unregister_react_panic`, `module init register_react_panic`.
• 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.