lib/notifier-error-inject.h
Source file repositories/reference/linux-study-clean/lib/notifier-error-inject.h
File Facts
- System
- Linux kernel
- Corpus path
lib/notifier-error-inject.h- Extension
.h- Size
- 653 bytes
- Lines
- 26
- Domain
- Kernel Services
- Bucket
- lib
- Inferred role
- Kernel Services: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/atomic.hlinux/debugfs.hlinux/notifier.h
Detected Declarations
struct notifier_err_inject_actionstruct notifier_err_inject
Annotated Snippet
struct notifier_err_inject_action {
unsigned long val;
int error;
const char *name;
};
#define NOTIFIER_ERR_INJECT_ACTION(action) \
.name = #action, .val = (action),
struct notifier_err_inject {
struct notifier_block nb;
struct notifier_err_inject_action actions[];
/* The last slot must be terminated with zero sentinel */
};
extern struct dentry *notifier_err_inject_dir;
extern struct dentry *notifier_err_inject_init(const char *name,
struct dentry *parent, struct notifier_err_inject *err_inject,
int priority);
Annotation
- Immediate include surface: `linux/atomic.h`, `linux/debugfs.h`, `linux/notifier.h`.
- Detected declarations: `struct notifier_err_inject_action`, `struct notifier_err_inject`.
- Atlas domain: Kernel Services / lib.
- Implementation status: source 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.