crypto/arc4.c

File Facts

System

Linux kernel

Corpus path

crypto/arc4.c

Extension

.c

Size

2054 bytes

Lines

83

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/arc4.h
• crypto/internal/skcipher.h
• linux/init.h
• linux/kernel.h
• linux/module.h
• linux/sched.h

Detected Declarations

• function crypto_arc4_setkey
• function crypto_arc4_crypt
• function crypto_arc4_init
• function arc4_init
• function arc4_exit
• module init arc4_init

Annotated Snippet

module_init(arc4_init);
module_exit(arc4_exit);

MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("ARC4 Cipher Algorithm");
MODULE_AUTHOR("Jon Oberheide <jon@oberheide.org>");
MODULE_ALIAS_CRYPTO("ecb(arc4)");

Annotation

• Immediate include surface: `crypto/arc4.h`, `crypto/internal/skcipher.h`, `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/sched.h`.
• Detected declarations: `function crypto_arc4_setkey`, `function crypto_arc4_crypt`, `function crypto_arc4_init`, `function arc4_init`, `function arc4_exit`, `module init arc4_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.