crypto/rmd160.c

Source file repositories/reference/linux-study-clean/crypto/rmd160.c

File Facts

System: Linux kernel
Corpus path: crypto/rmd160.c
Extension: .c
Size: 12531 bytes
Lines: 352
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

crypto/internal/hash.h
linux/kernel.h
linux/module.h
linux/string.h
ripemd.h

Detected Declarations

struct rmd160_ctx
function rmd160_transform
function rmd160_init
function rmd160_update
function rmd160_finup
function rmd160_mod_init
function rmd160_mod_fini
module init rmd160_mod_init

Annotated Snippet

module_init(rmd160_mod_init);
module_exit(rmd160_mod_fini);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Adrian-Ken Rueegsegger <ken@codelabs.ch>");
MODULE_DESCRIPTION("RIPEMD-160 Message Digest");
MODULE_ALIAS_CRYPTO("rmd160");

Annotation

Immediate include surface: `crypto/internal/hash.h`, `linux/kernel.h`, `linux/module.h`, `linux/string.h`, `ripemd.h`.
Detected declarations: `struct rmd160_ctx`, `function rmd160_transform`, `function rmd160_init`, `function rmd160_update`, `function rmd160_finup`, `function rmd160_mod_init`, `function rmd160_mod_fini`, `module init rmd160_mod_init`.
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.