include/uapi/linux/random.h
Source file repositories/reference/linux-study-clean/include/uapi/linux/random.h
File Facts
- System
- Linux kernel
- Corpus path
include/uapi/linux/random.h- Extension
.h- Size
- 1912 bytes
- Lines
- 74
- 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/types.hlinux/ioctl.hlinux/irqnr.h
Detected Declarations
struct rand_pool_infostruct vgetrandom_opaque_params
Annotated Snippet
struct rand_pool_info {
int entropy_count;
int buf_size;
__u32 buf[];
};
/*
* Flags for getrandom(2)
*
* GRND_NONBLOCK Don't block and return EAGAIN instead
* GRND_RANDOM No effect
* GRND_INSECURE Return non-cryptographic random bytes
*/
#define GRND_NONBLOCK 0x0001
#define GRND_RANDOM 0x0002
#define GRND_INSECURE 0x0004
/**
* struct vgetrandom_opaque_params - arguments for allocating memory for vgetrandom
*
* @size_per_opaque_state: Size of each state that is to be passed to vgetrandom().
* @mmap_prot: Value of the prot argument in mmap(2).
* @mmap_flags: Value of the flags argument in mmap(2).
* @reserved: Reserved for future use.
*/
struct vgetrandom_opaque_params {
__u32 size_of_opaque_state;
__u32 mmap_prot;
__u32 mmap_flags;
__u32 reserved[13];
};
#endif /* _UAPI_LINUX_RANDOM_H */
Annotation
- Immediate include surface: `linux/types.h`, `linux/ioctl.h`, `linux/irqnr.h`.
- Detected declarations: `struct rand_pool_info`, `struct vgetrandom_opaque_params`.
- 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.