crypto/ecdh.c

File Facts

System

Linux kernel

Corpus path

crypto/ecdh.c

Extension

.c

Size

5970 bytes

Lines

248

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• crypto/internal/ecc.h
• crypto/internal/kpp.h
• crypto/kpp.h
• crypto/ecdh.h
• linux/scatterlist.h

Detected Declarations

• struct ecdh_ctx
• function ecdh_set_secret
• function ecdh_compute_value
• function ecdh_max_size
• function ecdh_nist_p192_init_tfm
• function ecdh_nist_p256_init_tfm
• function ecdh_nist_p384_init_tfm
• function ecdh_init
• function ecdh_exit
• module init ecdh_init

Annotated Snippet

module_init(ecdh_init);
module_exit(ecdh_exit);
MODULE_ALIAS_CRYPTO("ecdh");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("ECDH generic algorithm");

Annotation

• Immediate include surface: `linux/module.h`, `crypto/internal/ecc.h`, `crypto/internal/kpp.h`, `crypto/kpp.h`, `crypto/ecdh.h`, `linux/scatterlist.h`.
• Detected declarations: `struct ecdh_ctx`, `function ecdh_set_secret`, `function ecdh_compute_value`, `function ecdh_max_size`, `function ecdh_nist_p192_init_tfm`, `function ecdh_nist_p256_init_tfm`, `function ecdh_nist_p384_init_tfm`, `function ecdh_init`, `function ecdh_exit`, `module init ecdh_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.