include/linux/sched/coredump.h
Source file repositories/reference/linux-study-clean/include/linux/sched/coredump.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/sched/coredump.h- Extension
.h- Size
- 715 bytes
- Lines
- 20
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
enum task_dumpable
Annotated Snippet
#ifndef _LINUX_SCHED_COREDUMP_H
#define _LINUX_SCHED_COREDUMP_H
/*
* Task dumpability mode. Gates core dump production and ptrace_attach()
* authorization. The numeric values are stable ABI (suid_dumpable
* sysctl, prctl(PR_SET_DUMPABLE)); do not renumber.
*/
enum task_dumpable {
TASK_DUMPABLE_OFF = 0, /* no dump; ptrace needs CAP_SYS_PTRACE */
TASK_DUMPABLE_OWNER = 1, /* default; dump and ptrace by uid match */
TASK_DUMPABLE_ROOT = 2, /* dump as root; ptrace needs CAP_SYS_PTRACE */
};
void task_exec_state_set_dumpable(enum task_dumpable value);
enum task_dumpable task_exec_state_get_dumpable(struct task_struct *task);
#endif /* _LINUX_SCHED_COREDUMP_H */
Annotation
- Detected declarations: `enum task_dumpable`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.