include/linux/scs.h

File Facts

System

Linux kernel

Corpus path

include/linux/scs.h

Extension

.h

Size

2308 bytes

Lines

87

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/gfp.h
• linux/poison.h
• linux/sched.h
• linux/sizes.h

Detected Declarations

• function scs_task_reset
• function task_scs_end_corrupted
• function scs_is_dynamic
• function scs_is_enabled
• function scs_free
• function scs_release
• function scs_is_enabled
• function scs_is_dynamic

Annotated Snippet

static inline void scs_free(void *s) {}
static inline void scs_init(void) {}
static inline void scs_task_reset(struct task_struct *tsk) {}
static inline int scs_prepare(struct task_struct *tsk, int node) { return 0; }
static inline void scs_release(struct task_struct *tsk) {}
static inline bool task_scs_end_corrupted(struct task_struct *tsk) { return false; }
static inline bool scs_is_enabled(void) { return false; }
static inline bool scs_is_dynamic(void) { return false; }

#endif /* CONFIG_SHADOW_CALL_STACK */

#endif /* _LINUX_SCS_H */

Annotation

• Immediate include surface: `linux/gfp.h`, `linux/poison.h`, `linux/sched.h`, `linux/sizes.h`.
• Detected declarations: `function scs_task_reset`, `function task_scs_end_corrupted`, `function scs_is_dynamic`, `function scs_is_enabled`, `function scs_free`, `function scs_release`, `function scs_is_enabled`, `function scs_is_dynamic`.
• 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.