include/uapi/linux/loadpin.h

Source file repositories/reference/linux-study-clean/include/uapi/linux/loadpin.h

File Facts

System: Linux kernel
Corpus path: include/uapi/linux/loadpin.h
Extension: .h
Size: 849 bytes
Lines: 23
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 _UAPI_LINUX_LOOP_LOADPIN_H
#define _UAPI_LINUX_LOOP_LOADPIN_H

#define LOADPIN_IOC_MAGIC	'L'

/**
 * LOADPIN_IOC_SET_TRUSTED_VERITY_DIGESTS - Set up the root digests of verity devices
 *                                          that loadpin should trust.
 *
 * Takes a file descriptor from which to read the root digests of trusted verity devices. The file
 * is expected to contain a list of digests in ASCII format, with one line per digest. The ioctl
 * must be issued on the securityfs attribute 'loadpin/dm-verity' (which can be typically found
 * under /sys/kernel/security/loadpin/dm-verity).
 */
#define LOADPIN_IOC_SET_TRUSTED_VERITY_DIGESTS _IOW(LOADPIN_IOC_MAGIC, 0x00, unsigned int)

#endif /* _UAPI_LINUX_LOOP_LOADPIN_H */

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.