include/linux/sem.h
Source file repositories/reference/linux-study-clean/include/linux/sem.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/sem.h- Extension
.h- Size
- 495 bytes
- Lines
- 29
- 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
uapi/linux/sem.hlinux/sem_types.h
Detected Declarations
struct task_structfunction copy_semundofunction exit_sem
Annotated Snippet
#ifndef _LINUX_SEM_H
#define _LINUX_SEM_H
#include <uapi/linux/sem.h>
#include <linux/sem_types.h>
struct task_struct;
#ifdef CONFIG_SYSVIPC
extern int copy_semundo(u64 clone_flags, struct task_struct *tsk);
extern void exit_sem(struct task_struct *tsk);
#else
static inline int copy_semundo(u64 clone_flags, struct task_struct *tsk)
{
return 0;
}
static inline void exit_sem(struct task_struct *tsk)
{
return;
}
#endif
#endif /* _LINUX_SEM_H */
Annotation
- Immediate include surface: `uapi/linux/sem.h`, `linux/sem_types.h`.
- Detected declarations: `struct task_struct`, `function copy_semundo`, `function exit_sem`.
- 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.