kernel/locking/irqflag-debug.c
Source file repositories/reference/linux-study-clean/kernel/locking/irqflag-debug.c
File Facts
- System
- Linux kernel
- Corpus path
kernel/locking/irqflag-debug.c- Extension
.c- Size
- 324 bytes
- Lines
- 14
- 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.
Dependency Surface
linux/bug.hlinux/export.hlinux/irqflags.h
Detected Declarations
function warn_bogus_irq_restoreexport warn_bogus_irq_restore
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
#include <linux/bug.h>
#include <linux/export.h>
#include <linux/irqflags.h>
noinstr void warn_bogus_irq_restore(void)
{
instrumentation_begin();
WARN_ONCE(1, "raw_local_irq_restore() called with IRQs enabled\n");
instrumentation_end();
}
EXPORT_SYMBOL(warn_bogus_irq_restore);
Annotation
- Immediate include surface: `linux/bug.h`, `linux/export.h`, `linux/irqflags.h`.
- Detected declarations: `function warn_bogus_irq_restore`, `export warn_bogus_irq_restore`.
- 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.