crypto/seed.c

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

File Facts

System: Linux kernel
Corpus path: crypto/seed.c
Extension: .c
Size: 17562 bytes
Lines: 470
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/algapi.h
linux/module.h
linux/init.h
linux/types.h
linux/errno.h
linux/unaligned.h

Detected Declarations

struct seed_ctx
function Copyright
function seed_set_key
function seed_encrypt
function seed_decrypt
function seed_init
function seed_fini
module init seed_init

Annotated Snippet

module_init(seed_init);
module_exit(seed_fini);

MODULE_DESCRIPTION("SEED Cipher Algorithm");
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Hye-Shik Chang <perky@FreeBSD.org>, Kim Hyun <hkim@kisa.or.kr>");
MODULE_ALIAS_CRYPTO("seed");

Annotation

Immediate include surface: `crypto/algapi.h`, `linux/module.h`, `linux/init.h`, `linux/types.h`, `linux/errno.h`, `linux/unaligned.h`.
Detected declarations: `struct seed_ctx`, `function Copyright`, `function seed_set_key`, `function seed_encrypt`, `function seed_decrypt`, `function seed_init`, `function seed_fini`, `module init seed_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.