lib/zstd/decompress_sources.h

File Facts

System

Linux kernel

Corpus path

lib/zstd/decompress_sources.h

Extension

.h

Size

1146 bytes

Lines

35

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: implementation source

Status

source 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.

Dependency Surface

• common/debug.c
• common/entropy_common.c
• common/error_private.c
• common/fse_decompress.c
• common/zstd_common.c
• decompress/huf_decompress.c
• decompress/zstd_ddict.c
• decompress/zstd_decompress.c
• decompress/zstd_decompress_block.c
• zstd_decompress_module.c

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#define ZSTD_DISABLE_ASM 1

#include "common/debug.c"
#include "common/entropy_common.c"
#include "common/error_private.c"
#include "common/fse_decompress.c"
#include "common/zstd_common.c"
#include "decompress/huf_decompress.c"
#include "decompress/zstd_ddict.c"
#include "decompress/zstd_decompress.c"
#include "decompress/zstd_decompress_block.c"
#include "zstd_decompress_module.c"

Annotation

• Immediate include surface: `common/debug.c`, `common/entropy_common.c`, `common/error_private.c`, `common/fse_decompress.c`, `common/zstd_common.c`, `decompress/huf_decompress.c`, `decompress/zstd_ddict.c`, `decompress/zstd_decompress.c`.
• Atlas domain: Kernel Services / lib.
• Implementation status: source 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.