include/linux/sys.h
Source file repositories/reference/linux-study-clean/include/linux/sys.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/sys.h- Extension
.h- Size
- 960 bytes
- Lines
- 31
- 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.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _LINUX_SYS_H
#define _LINUX_SYS_H
/*
* This file is no longer used or needed
*/
/*
* These are system calls that will be removed at some time
* due to newer versions existing..
* (please be careful - ibcs2 may need some of these).
*/
#ifdef notdef
#define _sys_waitpid _sys_old_syscall /* _sys_wait4 */
#define _sys_olduname _sys_old_syscall /* _sys_newuname */
#define _sys_uname _sys_old_syscall /* _sys_newuname */
#define _sys_stat _sys_old_syscall /* _sys_newstat */
#define _sys_fstat _sys_old_syscall /* _sys_newfstat */
#define _sys_lstat _sys_old_syscall /* _sys_newlstat */
#define _sys_signal _sys_old_syscall /* _sys_sigaction */
#define _sys_sgetmask _sys_old_syscall /* _sys_sigprocmask */
#define _sys_ssetmask _sys_old_syscall /* _sys_sigprocmask */
#endif
/*
* These are system calls that haven't been implemented yet
* but have an entry in the table for future expansion..
*/
#endif
Annotation
- 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.