crypto/wp512.c
Source file repositories/reference/linux-study-clean/crypto/wp512.c
File Facts
- System
- Linux kernel
- Corpus path
crypto/wp512.c- Extension
.c- Size
- 60354 bytes
- Lines
- 1146
- 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.hlinux/init.hlinux/kernel.hlinux/module.hlinux/string.hlinux/unaligned.h
Detected Declarations
struct wp512_ctxfunction wp512_process_bufferfunction wp512_initfunction wp512_add_lengthfunction wp512_updatefunction wp512_finupfunction wp384_finupfunction wp256_finupfunction wp512_mod_initfunction wp512_mod_finimodule init wp512_mod_init
Annotated Snippet
module_init(wp512_mod_init);
module_exit(wp512_mod_fini);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Whirlpool Message Digest Algorithm");Annotation
- Immediate include surface: `crypto/internal/hash.h`, `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/string.h`, `linux/unaligned.h`.
- Detected declarations: `struct wp512_ctx`, `function wp512_process_buffer`, `function wp512_init`, `function wp512_add_length`, `function wp512_update`, `function wp512_finup`, `function wp384_finup`, `function wp256_finup`, `function wp512_mod_init`, `function wp512_mod_fini`.
- 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.