lib/notifier-error-inject.c

File Facts

System

Linux kernel

Corpus path

lib/notifier-error-inject.c

Extension

.c

Size

2523 bytes

Lines

100

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• notifier-error-inject.h

Detected Declarations

• function debugfs_errno_set
• function debugfs_errno_get
• function notifier_err_inject_callback
• function err_inject_init
• function err_inject_exit
• module init err_inject_init
• export notifier_err_inject_dir
• export notifier_err_inject_init

Annotated Snippet

module_init(err_inject_init);
module_exit(err_inject_exit);

MODULE_DESCRIPTION("Notifier error injection module");
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Akinobu Mita <akinobu.mita@gmail.com>");

Annotation

• Immediate include surface: `linux/module.h`, `notifier-error-inject.h`.
• Detected declarations: `function debugfs_errno_set`, `function debugfs_errno_get`, `function notifier_err_inject_callback`, `function err_inject_init`, `function err_inject_exit`, `module init err_inject_init`, `export notifier_err_inject_dir`, `export notifier_err_inject_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.