tools/lib/bpf/zip.h

File Facts

System

Linux kernel

Corpus path

tools/lib/bpf/zip.h

Extension

.h

Size

1272 bytes

Lines

48

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct zip_archive
• struct zip_entry

Annotated Snippet

struct zip_entry {
	/* Compression method as defined in pkzip spec. 0 means data is uncompressed. */
	__u16 compression;

	/* Non-null terminated name of the file. */
	const char *name;
	/* Length of the file name. */
	__u16 name_length;

	/* Pointer to the file data. */
	const void *data;
	/* Length of the file data. */
	__u32 data_length;
	/* Offset of the file data within the archive. */
	__u32 data_offset;
};

/* Open a zip archive. Returns NULL in case of an error. */
struct zip_archive *zip_archive_open(const char *path);

/* Close a zip archive and release resources. */
void zip_archive_close(struct zip_archive *archive);

/* Look up an entry corresponding to a file in given zip archive. */
int zip_archive_find_entry(struct zip_archive *archive, const char *name, struct zip_entry *out);

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct zip_archive`, `struct zip_entry`.
• Atlas domain: Support Tooling And Documentation / tools.
• 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.