arch/arm/crypto/aes-neonbs-glue.c
Source file repositories/reference/linux-study-clean/arch/arm/crypto/aes-neonbs-glue.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/crypto/aes-neonbs-glue.c- Extension
.c- Size
- 10844 bytes
- Lines
- 415
- Domain
- Architecture Layer
- Bucket
- arch/arm
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- 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
asm/neon.hasm/simd.hcrypto/aes.hcrypto/internal/skcipher.hcrypto/scatterwalk.hcrypto/xts.hlinux/module.h
Detected Declarations
struct aesbs_ctxstruct aesbs_cbc_ctxstruct aesbs_xts_ctxfunction aesbs_setkeyfunction __ecb_cryptfunction ecb_encryptfunction ecb_decryptfunction aesbs_cbc_setkeyfunction cbc_encryptfunction cbc_decryptfunction ctr_encryptfunction aesbs_xts_setkeyfunction __xts_cryptfunction xts_encryptfunction xts_decryptfunction aes_exitfunction aes_initmodule init aes_init
Annotated Snippet
module_init(aes_init);
module_exit(aes_exit);Annotation
- Immediate include surface: `asm/neon.h`, `asm/simd.h`, `crypto/aes.h`, `crypto/internal/skcipher.h`, `crypto/scatterwalk.h`, `crypto/xts.h`, `linux/module.h`.
- Detected declarations: `struct aesbs_ctx`, `struct aesbs_cbc_ctx`, `struct aesbs_xts_ctx`, `function aesbs_setkey`, `function __ecb_crypt`, `function ecb_encrypt`, `function ecb_decrypt`, `function aesbs_cbc_setkey`, `function cbc_encrypt`, `function cbc_decrypt`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.