security/integrity/ima/ima_mok.c
Source file repositories/reference/linux-study-clean/security/integrity/ima/ima_mok.c
File Facts
- System
- Linux kernel
- Corpus path
security/integrity/ima/ima_mok.c- Extension
.c- Size
- 1179 bytes
- Lines
- 50
- Domain
- Core OS
- Bucket
- Security And Isolation
- Inferred role
- Core OS: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/export.hlinux/kernel.hlinux/sched.hlinux/cred.hlinux/err.hlinux/init.hlinux/slab.hkeys/system_keyring.h
Detected Declarations
function ima_mok_initmodule init ima_mok_init
Annotated Snippet
device_initcall(ima_mok_init);Annotation
- Immediate include surface: `linux/export.h`, `linux/kernel.h`, `linux/sched.h`, `linux/cred.h`, `linux/err.h`, `linux/init.h`, `linux/slab.h`, `keys/system_keyring.h`.
- Detected declarations: `function ima_mok_init`, `module init ima_mok_init`.
- Atlas domain: Core OS / Security And Isolation.
- Implementation status: integration 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.