crypto/fips.c
Source file repositories/reference/linux-study-clean/crypto/fips.c
File Facts
- System
- Linux kernel
- Corpus path
crypto/fips.c- Extension
.c- Size
- 2170 bytes
- Lines
- 103
- Domain
- Kernel Services
- Bucket
- crypto
- Inferred role
- Kernel Services: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
- Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/export.hlinux/fips.hlinux/init.hlinux/module.hlinux/kernel.hlinux/sysctl.hlinux/notifier.hlinux/string_choices.hgenerated/utsrelease.h
Detected Declarations
function fips_enablefunction crypto_proc_fips_initfunction crypto_proc_fips_exitfunction fips_fail_notifyfunction fips_initfunction fips_exitmodule init fips_initexport fips_enabledexport fips_fail_notif_chainexport fips_fail_notify
Annotated Snippet
module_init(fips_init);
module_exit(fips_exit);Annotation
- Immediate include surface: `linux/export.h`, `linux/fips.h`, `linux/init.h`, `linux/module.h`, `linux/kernel.h`, `linux/sysctl.h`, `linux/notifier.h`, `linux/string_choices.h`.
- Detected declarations: `function fips_enable`, `function crypto_proc_fips_init`, `function crypto_proc_fips_exit`, `function fips_fail_notify`, `function fips_init`, `function fips_exit`, `module init fips_init`, `export fips_enabled`, `export fips_fail_notif_chain`, `export fips_fail_notify`.
- Atlas domain: Kernel Services / crypto.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.