lib/crypto/chacha.c

File Facts

System

Linux kernel

Corpus path

lib/crypto/chacha.c

Extension

.c

Size

1726 bytes

Lines

71

Domain

Kernel Services

Bucket

lib

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

• crypto/chacha.h
• crypto/utils.h
• linux/export.h
• linux/kernel.h
• linux/module.h
• chacha.h

Detected Declarations

• function cipher
• function chacha_crypt
• function hchacha_block
• function chacha_mod_init
• function chacha_mod_exit
• module init chacha_mod_init
• export chacha_crypt
• export hchacha_block

Annotated Snippet

subsys_initcall(chacha_mod_init);

static void __exit chacha_mod_exit(void)
{
}
module_exit(chacha_mod_exit);
#endif

MODULE_DESCRIPTION("ChaCha stream cipher (RFC7539)");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `crypto/chacha.h`, `crypto/utils.h`, `linux/export.h`, `linux/kernel.h`, `linux/module.h`, `chacha.h`.
• Detected declarations: `function cipher`, `function chacha_crypt`, `function hchacha_block`, `function chacha_mod_init`, `function chacha_mod_exit`, `module init chacha_mod_init`, `export chacha_crypt`, `export hchacha_block`.
• Atlas domain: Kernel Services / lib.
• 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.