include/linux/sched/exec_state.h
Source file repositories/reference/linux-study-clean/include/linux/sched/exec_state.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/sched/exec_state.h- Extension
.h- Size
- 1050 bytes
- Lines
- 32
- 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
linux/init.hlinux/rcupdate.hlinux/refcount.hlinux/sched/coredump.hlinux/user_namespace.h
Detected Declarations
struct task_exec_state
Annotated Snippet
struct task_exec_state {
refcount_t count;
enum task_dumpable dumpable;
struct user_namespace *user_ns;
struct rcu_head rcu;
};
extern struct task_exec_state init_task_exec_state;
struct task_exec_state *alloc_task_exec_state(struct user_namespace *user_ns);
void put_task_exec_state(struct task_exec_state *exec_state);
struct task_exec_state *task_exec_state_rcu(const struct task_struct *tsk);
struct task_exec_state *task_exec_state_replace(struct task_struct *tsk,
struct task_exec_state *exec_state);
int task_exec_state_copy(struct task_struct *tsk);
void __init exec_state_init(void);
DEFINE_FREE(put_task_exec_state, struct task_exec_state *, put_task_exec_state(_T))
#endif /* _LINUX_SCHED_EXEC_STATE_H */
Annotation
- Immediate include surface: `linux/init.h`, `linux/rcupdate.h`, `linux/refcount.h`, `linux/sched/coredump.h`, `linux/user_namespace.h`.
- Detected declarations: `struct task_exec_state`.
- 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.