crypto/kdf_sp800108.c

File Facts

System

Linux kernel

Corpus path

crypto/kdf_sp800108.c

Extension

.c

Size

3737 bytes

Lines

158

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/fips.h
• linux/module.h
• crypto/kdf_sp800108.h
• crypto/internal/kdf_selftest.h

Detected Declarations

• function Copyright
• function crypto_kdf108_setkey
• function crypto_kdf108_init
• function crypto_kdf108_exit
• module init crypto_kdf108_init
• export crypto_kdf108_ctr_generate
• export crypto_kdf108_setkey

Annotated Snippet

module_init(crypto_kdf108_init);
module_exit(crypto_kdf108_exit);

MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Stephan Mueller <smueller@chronox.de>");
MODULE_DESCRIPTION("Key Derivation Function conformant to SP800-108");

Annotation

• Immediate include surface: `linux/fips.h`, `linux/module.h`, `crypto/kdf_sp800108.h`, `crypto/internal/kdf_selftest.h`.
• Detected declarations: `function Copyright`, `function crypto_kdf108_setkey`, `function crypto_kdf108_init`, `function crypto_kdf108_exit`, `module init crypto_kdf108_init`, `export crypto_kdf108_ctr_generate`, `export crypto_kdf108_setkey`.
• Atlas domain: Kernel Services / crypto.
• 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.