crypto/lzo.c

File Facts

System

Linux kernel

Corpus path

crypto/lzo.c

Extension

.c

Size

2009 bytes

Lines

102

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

• crypto/internal/scompress.h
• linux/init.h
• linux/lzo.h
• linux/module.h
• linux/slab.h

Detected Declarations

• function lzo_free_ctx
• function __lzo_compress
• function lzo_scompress
• function __lzo_decompress
• function lzo_sdecompress
• function lzo_mod_init
• function lzo_mod_fini
• module init lzo_mod_init

Annotated Snippet

module_init(lzo_mod_init);
module_exit(lzo_mod_fini);

MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("LZO Compression Algorithm");
MODULE_ALIAS_CRYPTO("lzo");

Annotation

• Immediate include surface: `crypto/internal/scompress.h`, `linux/init.h`, `linux/lzo.h`, `linux/module.h`, `linux/slab.h`.
• Detected declarations: `function lzo_free_ctx`, `function __lzo_compress`, `function lzo_scompress`, `function __lzo_decompress`, `function lzo_sdecompress`, `function lzo_mod_init`, `function lzo_mod_fini`, `module init lzo_mod_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.