arch/x86/kernel/dumpstack_32.c
Source file repositories/reference/linux-study-clean/arch/x86/kernel/dumpstack_32.c
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/kernel/dumpstack_32.c- Extension
.c- Size
- 3578 bytes
- Lines
- 156
- Domain
- Architecture Layer
- Bucket
- arch/x86
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/sched/debug.hlinux/kallsyms.hlinux/kprobes.hlinux/uaccess.hlinux/hardirq.hlinux/kdebug.hlinux/export.hlinux/ptrace.hlinux/kexec.hlinux/sysfs.hlinux/bug.hlinux/nmi.hasm/stacktrace.h
Detected Declarations
function Copyrightfunction in_hardirq_stackfunction in_softirq_stackfunction in_doublefault_stackfunction get_stack_info
Annotated Snippet
if (*visit_mask & (1UL << info->type)) {
printk_deferred_once(KERN_WARNING "WARNING: stack recursion on stack type %d\n", info->type);
goto unknown;
}
*visit_mask |= 1UL << info->type;
}
return 0;
unknown:
info->type = STACK_TYPE_UNKNOWN;
return -EINVAL;
}
Annotation
- Immediate include surface: `linux/sched/debug.h`, `linux/kallsyms.h`, `linux/kprobes.h`, `linux/uaccess.h`, `linux/hardirq.h`, `linux/kdebug.h`, `linux/export.h`, `linux/ptrace.h`.
- Detected declarations: `function Copyright`, `function in_hardirq_stack`, `function in_softirq_stack`, `function in_doublefault_stack`, `function get_stack_info`.
- Atlas domain: Architecture Layer / arch/x86.
- 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.