include/linux/restart_block.h
Source file repositories/reference/linux-study-clean/include/linux/restart_block.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/restart_block.h- Extension
.h- Size
- 1128 bytes
- Lines
- 62
- 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/compiler.hlinux/time64.hlinux/types.h
Detected Declarations
struct __kernel_timespecstruct timespecstruct old_timespec32struct pollfdstruct restart_blockenum timespec_type
Annotated Snippet
struct restart_block {
unsigned long arch_data;
long (*fn)(struct restart_block *);
union {
/* For futex_wait() */
struct {
u32 __user *uaddr;
u32 val;
u32 flags;
u32 bitset;
ktime_t time;
u32 __user *uaddr2;
} futex;
/* For nanosleep */
struct {
clockid_t clockid;
enum timespec_type type;
union {
struct __kernel_timespec __user *rmtp;
struct old_timespec32 __user *compat_rmtp;
};
ktime_t expires;
} nanosleep;
/* For poll */
struct {
struct pollfd __user *ufds;
int nfds;
int has_timeout;
struct timespec64 end_time;
} poll;
};
};
extern long do_no_restart_syscall(struct restart_block *parm);
#endif /* __LINUX_RESTART_BLOCK_H */
Annotation
- Immediate include surface: `linux/compiler.h`, `linux/time64.h`, `linux/types.h`.
- Detected declarations: `struct __kernel_timespec`, `struct timespec`, `struct old_timespec32`, `struct pollfd`, `struct restart_block`, `enum timespec_type`.
- 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.