crypto/sm4_generic.c

File Facts

System

Linux kernel

Corpus path

crypto/sm4_generic.c

Extension

.c

Size

2142 bytes

Lines

93

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
• crypto/sm4.h
• linux/module.h
• linux/init.h
• linux/types.h
• linux/errno.h
• asm/byteorder.h
• linux/unaligned.h

Detected Declarations

• function sm4_setkey
• function sm4_encrypt
• function sm4_decrypt
• function sm4_init
• function sm4_fini
• module init sm4_init

Annotated Snippet

module_init(sm4_init);
module_exit(sm4_fini);

MODULE_DESCRIPTION("SM4 Cipher Algorithm");
MODULE_LICENSE("GPL v2");
MODULE_ALIAS_CRYPTO("sm4");
MODULE_ALIAS_CRYPTO("sm4-generic");

Annotation

• Immediate include surface: `crypto/algapi.h`, `crypto/sm4.h`, `linux/module.h`, `linux/init.h`, `linux/types.h`, `linux/errno.h`, `asm/byteorder.h`, `linux/unaligned.h`.
• Detected declarations: `function sm4_setkey`, `function sm4_encrypt`, `function sm4_decrypt`, `function sm4_init`, `function sm4_fini`, `module init sm4_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.